Using multiple NFS server

[svasseur]

i want use 2 NFS server, with helm i launch
the first nfs-client

helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner \
--set nfs.server=172.20.20.93 \
--set nfs.path=/nfs

and another

helm install nfsbis-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner \
--set nfs.server=172.20.20.39 \
--set nfs.path=/nfs \
--set storageClass.name=nfs-clientbis \
--set storageClass.provisionerName=nfsbis-subdir-external-provisioner
when create a volume on the second nfs-clientbis in the pod logs i see the volume but it's create in the first nfs-client

I don't know if it's possible to do that
thanks

[yonatankahana]

sorry but i am not sure that i got what is your question
please show your volumes and pvc's and try to explain a bit more :)

[svasseur]

i try to install and use 2 nfs server, but all pvc request go to the first nfs server only

[yonatankahana]

attach the yaml of your pvc's

[svasseur]

nfsbis.txt

[yonatankahana]

please send yamls of both pvc's and both pv's

[svasseur]

nfs-subdir-external-provisioner.txt
nfs.txt
nfsbis-subdir-external-provisioner-nfs-subdir-external-provisio.txt
nfsbis.txt


and everything is create on the first server
`re7-ubuntu-nfs1:/nfs$ ls nfs

hello-nfs-pvc-612f8543-fb5b-4c35-8585-2b1e62b72693:

hello-nfsclientbis-pvc-f7a90ab8-c476-4ae4-bb4f-e105d8160e95:`

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.