Report this

What is the reason for this report?

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

Posted on August 10, 2019

Hi, trying to deploy this image https://github.com/helm/charts/tree/master/stable/wordpress 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!



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!

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.

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

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.