<p>I'm using Kubernetes and I recently updated my admin certs used in the <code>kubeconfig</code>. However, after I did that, all the <code>helm</code> commands fail thus:</p>

<pre><code>Error: Get https://cluster.mysite.com/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: x509: certificate signed by unknown authority
</code></pre>

<p><code>kubectl</code> works as expected:</p>

<pre><code>$ kubectl get nodes
NAME                                           STATUS    ROLES     AGE       VERSION
ip-10-1-0-34.eu-central-1.compute.internal     Ready     master    42d       v1.7.10+coreos.0
ip-10-1-1-51.eu-central-1.compute.internal     Ready     master    42d       v1.7.10+coreos.0
ip-10-1-10-120.eu-central-1.compute.internal   Ready     &lt;none&gt;    42d       v1.7.10+coreos.0
ip-10-1-10-135.eu-central-1.compute.internal   Ready     &lt;none&gt;    27d       v1.7.10+coreos.0
ip-10-1-11-71.eu-central-1.compute.internal    Ready     &lt;none&gt;    42d       v1.7.10+coreos.0
ip-10-1-12-199.eu-central-1.compute.internal   Ready     &lt;none&gt;    8d        v1.7.10+coreos.0
ip-10-1-2-110.eu-central-1.compute.internal    Ready     master    42d       v1.7.10+coreos.0
</code></pre>

<p>As far as I've been able to read, <code>helm</code> is supposed to use the same certificates as <code>kubectl</code>, which makes me curious as how how <code>kubectl</code> works, but <code>helm</code> doesn't?</p>

<p>This is a production cluster with internal releases handled through helm charts, so it being solved is imperative.</p>

<p>Any hints would be greatly appreciated.</p>

<p>As a workaround you can try to disable certificate verification. Helm uses the kube config file (by default <code>~/.kube/config</code>). You can add <code>insecure-skip-tls-verify: true</code> for the <code>cluster</code> section:</p>

<pre><code>clusters:
- cluster:
    server: https://cluster.mysite.com
    insecure-skip-tls-verify: true
  name: default
</code></pre>

<p>Did you already try to reinstall helm/tiller?</p>

<pre><code>kubectl delete deployment tiller-deploy --namespace kube-system
helm init
</code></pre>

<p>Also check if you have configured an invalid certificate in the cluster configuration.</p>
