<p>Try to remove the easyrsa relation with kubernetes-master in juju.</p>

<pre><code>juju remove-relation easyrsa kubernetes-master
</code></pre>

<p>Recreate it afterwards:</p>

<pre><code>juju add-relation easyrsa kubernetes-master
</code></pre>

<p>The certificate seems to be recreated for the master, which should now include it's clusterip (10.152.183.1) address as well in the SAN record of the certificate.</p>

CC BY-SA 4.0
2019-07-07T13:07:06.107Z
2019-07-07T13:07:06.107Z
hbogert
<p>I have lots of unexplained errors in kubernetes. Often I see errors in logs of pods with the following:</p>

<pre><code>Get https://10.152.183.1:443/api/v1/namespaces/{REDACTED}: x509: certificate is valid for 192.168.1.156, not 10.152.183.1}
</code></pre>

<p>I am using Canonical's distribution of Kubernetes deployed with Juju on a MAAS cluster. </p>

<kubernetes>
Why do many pods fail to communicate with the master
hbogert
# Why do many pods fail to communicate with the master

(Asked by: username_0 on 2019-07-07)

I have lots of unexplained errors in kubernetes. Often I see errors in logs of pods with the following:
Get https://10.152.183.1:443/api/v1/namespaces/{REDACTED}: x509: certificate is valid for 192.168.1.156, not 10.152.183.1}

I am using Canonical's distribution of Kubernetes deployed with Juju on a MAAS cluster.

**Tags:** kubernetes


---

## 1 answers

### Answer by username_0 on 2019-07-07. Score: 1

Try to remove the easyrsa relation with kubernetes-master in juju.
juju remove-relation easyrsa kubernetes-master

Recreate it afterwards:
juju add-relation easyrsa kubernetes-master

The certificate seems to be recreated for the master, which should now include it's clusterip (10.152.183.1) address as well in the SAN record of the certificate.


---

