Can the same k8s cluster deploy this driver multiple times

[yuenwah]

Is your feature request related to a problem?/Why is this needed
We may have multiple edge areas in the edge cluster, and each area uses its own nfs to create pvc. When csi-controller runs in other areas, pvc cannot be dynamically created in the current area, and an error message will be displayed saying that nfs cannot be connected because the network is not interoperable. This error message is in line with expectations.

Describe the solution you'd like in detail
Deploy multiple sets in one cluster, but it is necessary to consider whether daemonset csi-node can be shared, and use different drivers to distinguish csi-controllers.

Describe alternatives you've considered
null

Additional context
null

[andyzhangx]

pls try with this link: https://github.com/kubernetes-csi/csi-driver-nfs/tree/master/charts#install-driver-with-customized-driver-name-deployment-name,

[yuenwah]

pls try with this link: https://github.com/kubernetes-csi/csi-driver-nfs/tree/master/charts#install-driver-with-customized-driver-name-deployment-name,

We used this method for our first deployment, but we are not sure whether it is supported to deploy multiple times in the same cluster using this method.

[andyzhangx]

you need to test by yourself, I have not done that yet, pls verify and update whether there is any issue, thx.

[jsalatiel]

Wouldn't just create the storage classes manually allow to have multiple servers?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale