Skip to content
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

NFS server IP address changes - what should I do ? #355

Open
jackchuong opened this issue Sep 30, 2024 · 1 comment
Open

NFS server IP address changes - what should I do ? #355

jackchuong opened this issue Sep 30, 2024 · 1 comment

Comments

@jackchuong
Copy link

Hi all,
I deployed nfs-subdir-external-provisioner using helm to handle storage in a internal k8s cluster , NFS server is a QNAP device.
I need to change IP address of QNAP device, here my values yaml

nfs:
  server: "192.168.0.108"

I didn't use FQDN for server (my mistake) , what should I do if I need to change nfs server IP address to another ?
If I change it and upgrade helm chart, would it work ? What happen with existed PVC and PV ?
I don't want my data to be lost or corrupted. Please give me some advice, thank you very much.

@klaernie
Copy link

klaernie commented Oct 7, 2024

My recommendation would be for you to first upgrade using the new value and deploy a test pvc to ensure you made no typos and that the hostname you then use is actually working. This however won't touch your existing PVs, so you'll need to kubectl edit each of them and update the spec.nfs.server - or apply a patch with kubectl patch.

Just as an additional tip: if your old and new address are both equally reachable from your cluster I'd recommend you first add the new IP to the NFS server, patch the PVs, reboot your nodes to ensure they have the old NFS server not mounted anymore, and only then remove the old IP from your NFS server. Else you might run into the issue that your nodes trip up on the no longer reachable NFS server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants