Closed tdawe closed 1 week ago
@tdawe: Thank you for submitting this issue!
The issue is currently awaiting triage. Please make sure you have given us as much context as possible.
If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately.
We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at container.storage.modules@dell.com.
Note: I encountered this using my own build of the Powerflex driver and my own helm chart. I don't think that would change the results but I did not test it with the stock software. It worked when I added nasName: "" to the secret. I think just the documentation needs to be updated.
/sync
link: 30242
Bug Description
Documentation for PowerFlex nasName states it is not a required field: https://dell.github.io/csm-docs/docs/deployment/helm/drivers/installation/powerflex/
Deploying the driver without setting this field causes the node side of the driver to fail to start. Documentation needs to reflect that this field is "Required: true"
Logs
n/a
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
Don't set nasName in the PowerFlex secret.
Expected Behavior
Documentation is updated and correct regarding the nasName field.
CSM Driver(s)
PowerFlex
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
K8s
Operating System
n/a