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

Changing IP-Address of NFS Server #377

Open
inzanez opened this issue Mar 24, 2024 · 4 comments
Open

Changing IP-Address of NFS Server #377

inzanez opened this issue Mar 24, 2024 · 4 comments

Comments

@inzanez
Copy link

inzanez commented Mar 24, 2024

Hi

I just had to move an NFS server connected through democratic-csi to our Kubernetes cluster to a different network. Is there any easy way to change the IP address of the target server,...? Or what should be done in a case like this?

I assume it would be preferreable to use DNS names instead of IP addresses for storage targets,...that way it could be moved?

@travisghansen
Copy link
Member

Yes DNS would be preferred. I have a tool to migrate them here: https://github.com/democratic-csi/democratic-csi/blob/master/contrib/pv-updater.sh

It is a fairly precarious process so please read through the code and review what it does. After that run it on a test pv and just make sure it's doing everything you need.

@inzanez
Copy link
Author

inzanez commented Mar 24, 2024

Oh, I see. Yes, I will do so. But apart from changing the PVs (or to be more precise: delete them and re-create them),...I would also have to update the democratic-csi installation with a new server location. I guess this works without uninstall / re-install?
I just want to prevent existing PVCs from being deleted,...:-)

@travisghansen
Copy link
Member

You can safely roll out the new config, the existing items won't be deleted unless you delete the respective pvc/pv. Assuming the nas is available at both IPs for a period of time the existing volumes will continue to mount etc and new volumes will get the new endpoint. When you're ready just start migrating the old PVs to the new endpoint and then eventually when ready you can remove the old IP from the nas entirely.

@inzanez
Copy link
Author

inzanez commented Mar 25, 2024

For some reason I run into issues when making the NAS available at the second IP. Not quite sure what is happening, but all my PVs become inaccessible. Not sure if there is some asymmetric routing involved as the new NAS IP is in the same network as the Kubernetes workers. And so,...the responses might take a direct route,...? Although I was under the impression that this should not be an issue.
So maybe I'll have to shutdown everything and make the changes first,...

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