-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSM Operator Installation - Added CR fields for PowerMax and PowerFlex #1458
base: main
Are you sure you want to change the base?
Conversation
content/docs/getting-started/installation/kubernetes/powermax/csmoperator/_index.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No edits required
content/docs/getting-started/installation/kubernetes/powerflex/csmoperator/_index.md
Outdated
Show resolved
Hide resolved
content/docs/getting-started/installation/kubernetes/powerflex/csmoperator/_index.md
Outdated
Show resolved
Hide resolved
@@ -160,6 +160,7 @@ Example: | |||
| X_CSI_VSPHERE_PORTGROUP | Existing portGroup that driver will use for vSphere | Yes | "" | | |||
| X_CSI_VSPHERE_HOSTNAME | Existing host(initiator group)/host group(cascaded initiator group) that driver will use for vSphere | Yes | "" | | |||
| X_CSI_VCenter_HOST | URL/endpoint of the vCenter where all the ESX are present | Yes | "" | | |||
| X_CSI_POWERMAX_DEBUG | Enable/Disable gopowermax library-level debugging. | No | false | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to have this also added for other binding layers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed this comment with Aron:
gopowermax is the one being added with this PR, so we should be covered.
gopowerscale has:
https://github.com/dell/gopowerscale/blob/ef35bfd90f23593d67077d191328562ec17fc696/api/api.go#L58
but that isn't supported in operator at present.
goscaleio has the http flags, but like gopowerscale, they aren't currently supported in operator.
gopowerstore has:
https://github.com/dell/gopowerstore/blob/171b9c405d0d17e5cdaa2734c80f1637a4c01b5c/api/api.go#L138
and that is supported in operator: https://github.com/dell/csm-operator/blob/04fd860891c3f1ec640d24fbeaa273c18963aa95[…]/operatorconfig/driverconfig/powerstore/v2.13.0/controller.yaml
We don't currently expose that value in our Operator sample, nor do we call it out in csm-docs, but it is possible to add it like I did for the two flags already mentioned in this docs PR. Fairly trivial change in both repos, just add it to the docs tables and add a value to the samples in operator.
...
Per feedback, I am converting this PR to draft and working with my team to increase the scope of this defect and add granular control of library debug flags to other libraries.
Description
This PR adds documentation to support the changes made in dell/csm-operator#905 .
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist: