Question

Ingress / Helm on Kubernetes

Im looking to install the ingress controller on a DO managed K8 cluster. Im following : https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-with-cert-manager-on-digitalocean-kubernetes

Currently at the stage of installing Tiller (via https://www.digitalocean.com/community/tutorials/how-to-install-software-on-kubernetes-clusters-with-the-helm-package-manager) However, when I try to run the following, I get an error about it trying to hit the loopback. Like so,

root@abc123:/tmp# helm init --service-account tiller
$HELM_HOME has been configured at /root/.helm.
Error: error installing: Post http://localhost:8080/apis/extensions/v1beta1/namespaces/kube-system/deployments: dial tcp 127.0.0.1:8080: connect: connection refused

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.

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.

John Kwiatkoski • September 16, 2019

Hi there!

Do you currently have a working kubectl binary configured? Helm should use your currently configured kubectl:

From the helm docs (https://helm.sh/docs/install/#easy-in-cluster-installation): The easiest way to install tiller into the cluster is simply to run helm init. This will validate that helm’s local environment is set up correctly (and set it up if necessary). Then it will connect to whatever cluster kubectl connects to by default (kubectl config view).

I would check that kubectl is configured properly.

Regards,

John Kwiatkoski Senior Developer Support Engineer

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up