csm
csm copied to clipboard
dell
[FEATURE]: Add worker nodes' IP only
Describe the solution you'd like A clear and concise description of what you want to happen. When a pod attach a PVC, currently CSI controller will always to try add worker nodes' FQDN first, and then add IP if the FQDN resolution fails.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. CSI should skip trying FQDN, only try to add worker nodes' IP to Isilon, or provides an option for users who want to complete skip FQDN resolution.
Additional context Add any other context or screenshots about the feature request here. In Kuberentes env, it's a rare scenario in which worker nodes' IP changed while hostname/FQDN kept. Especially, when node's IP changes, the application/pod has to be moved to another node. It's not possible to continunously running pod while change the node IP. Which means the pod will reattach PVC and a new IP will be added to the NFS client. Thus it doesn't make any sense to try FQDN of worker nodes. While adding worker nodes FQDN limit our CSI use cases: In most of cases, the worker nodes' DNS resolution is internal and will not add to company's main DNS, nor via DNS delegation. It's time consuming for Isilon to try every FQDN and timeout. Especially, CSI controller processes these PVC attachment in sequential way. For a large kubenretes clusters, where have hundreds worker nodes and PVCare generated/attached frequently, this process can take 10 mins or more to finally attach the PVC, because each worker nodes for each PVC has to try FQDN and time out. In most of cases, application will report error because their timeout is shorter than our PVC attachment time.
@seanzhan2014: 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 assign an appropriate priority label.
We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected].
@HarishH-DELL I guess this is not a feature ask may be you need update here.
