helm dry run install

kubernetes kubernetes-helm
sfgroups picture sfgroups · Dec 19, 2017 · Viewed 51.1k times · Source

I am trying to test my development helm chat deployment output using --dry-run option. when I run the below command its trying to connect to Kubernetes API server.

Is dry run option required to connect Kubernetes cluster? all I want to check the deployment yaml file output.

helm install mychart-0.1.0.tgz --dry-run --debug

Error: Get http://localhost:8080/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.

Answer

Eldad Assis picture Eldad Assis · May 8, 2018

There is also an option to run helm template ./mychart to render the generated YAMLs without needing the connection to tiller. Combined with helm lint it's a great set to verify validity of your chart.

Related questions

How to pull environment variables with Helm charts

I have my deployment.yaml file within the templates directory of Helm charts with several environment variables for the container I will be running using Helm. Now I want to be able to pull the environment variables locally from whatever …

Read More
Pod status as `CreateContainerConfigError` in Minikube cluster

I am trying to run Sonarqube service using the following helm chart. So the set-up is like it starts a MySQL and Sonarqube service in the minikube cluster and Sonarqube service talks to the MySQL service to dump the data. …

Read More
helm list : cannot list configmaps in the namespace "kube-system"

I have installed helm 2.6.2 on the kubernetes 8 cluster. helm init worked fine. but when I run helm list it giving this error. helm list Error: configmaps is forbidden: User "system:serviceaccount:kube-system:default" cannot list configmaps in the namespace "kube-system" …

Read More