Question

Jenkins home volume persistence

Connected Tutorial
This question is a follow-up to this tutorial:

What happens to Jenkins volume in scenario where Jenkins pod is redeployed to another worker node? I assume in this example Jenkins volume (Jenkins state/data) persists only on worker node where it was deployed and not across the cluster. So when pod will be redeployed, all state will be lost?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi, yes, you are correct. If the pod get redeployed, the volume data would be lost in this case. To make the data persist, you can use a volume backed by something like NFS or a CSI driver. Here is a nice tutorial that talks about using NFS with DOKS: https://www.digitalocean.com/community/tutorials/how-to-set-up-readwritemany-rwx-persistent-volumes-with-nfs-on-digitalocean-kubernetes