Kubernetes Helm deployment via nfs-server-provisioner fails, connection refused

Hi, trying to deploy this image via Helm. It works fine with service.type = ClusterIP and persistence.storageClass = do-blockstorage or service.type = LoadBalancer and persistence.storageClass = nfs but fails with service.type = ClusterIP and persistence.storageClass = nfs, error Liveness probe failed.

Installed nfs via: helm install stable/nfs-server-provisioner --set persistence.enabled=true,persistence.size=10Gi

I think it’s probably not able to communicate via DNS.

Anyone have any ideas for a fix? Thanks!

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.

Accepted Answer

I didn’t wait long enough it works fine, sorry!

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.