<p dir="auto">I do <code class="notranslate">kube-push</code> to my cluster and meet the following issue:</p>
<ul dir="auto">
<li>In my push, I update control plane manifest as well as kubelet command line arguments.</li>
<li>After push, old static pods still running while new pods failed to run. Take apiserver as an example:
<ul dir="auto">
<li>There are 3 running containers after push: <code class="notranslate">old apiserver</code>, <code class="notranslate">old apiserver pause</code>, <code class="notranslate">new apiserver pause</code>.</li>
<li>Run <code class="notranslate">docker ps -a | grep apiserver</code> and find that new apiserver container exit because of error.</li>
</ul>
</li>
<li>To solve the problem, I do <code class="notranslate">docker rm -f</code> on <code class="notranslate">old apiserver</code> and <code class="notranslate">old apiserver pause</code> containers.</li>
</ul>
<p dir="auto">I think this should be fixed since there is high risk for <code class="notranslate">kube-push</code> failure.</p>
<p dir="auto">I'm getting this error on my Google Cloud cluster:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="I1117 22:56:55.385576    3509 kubelet.go:977] Unable to register kubernetes-minion-frx1 with the apiserver: Post https://kubernetes-master/api/v1/nodes: x509: cert
ificate signed by unknown authority"><pre class="notranslate"><code class="notranslate">I1117 22:56:55.385576    3509 kubelet.go:977] Unable to register kubernetes-minion-frx1 with the apiserver: Post https://kubernetes-master/api/v1/nodes: x509: cert
ificate signed by unknown authority
</code></pre></div>
<p dir="auto">Using the default <code class="notranslate">./cluster/kube-up.sh</code></p>
<p dir="auto">To reproduce:</p>
<ul dir="auto">
<li>kube-up</li>
<li>everything is working fine</li>
<li>delete one of the instances from the autoscaling group</li>
<li>the new instance will fail with this error continuously</li>
</ul>