<p>Since yesterday, I am struggling with this strange issue: node "kmaster" not found.
<a href="https://i.stack.imgur.com/VIqtp.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/VIqtp.png" alt="img_1"></a></p>

<p>I tried with multiple combinations of installing kubernetes on jetstream instance.</p>

<ol>
<li>using calico in ubuntu</li>
<li>using flannel in centos</li>
<li>and few other ways</li>
</ol>

<p>I looked it online and found many people have the same issue:
<a href="https://github.com/kubernetes/kubernetes/issues/61277" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/61277</a>
<a href="https://i.stack.imgur.com/dAupU.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/dAupU.png" alt="[kubeissue_2.jpg]"></a></p>

<p>If someone ran into a similar issue, then please let me know what steps are needed to be taken to resolve it.</p>

<p>Thanks.</p>

<p>I would recommend to bootstrap Kubernetes cluster from scratch and share with you some helpful links with steps how to proceed: </p>

<ul>
<li><a href="https://stackoverflow.com/questions/52720380/kubernetes-api-server-is-not-starting-on-a-single-kubeadm-cluster">Kubernetes cluster install on Ubuntu with Calico CNI</a></li>
<li><a href="https://stackoverflow.com/questions/53383994/error-marking-master-timed-out-waiting-for-the-condition-kubernetes/53410468#53410468">Kubernetes cluster install on Centos with Flannel CNI</a></li>
</ul>

<p>Keep in mind to fulfill system <a href="https://kubernetes.io/docs/setup/independent/install-kubeadm/#before-you-begin" rel="nofollow noreferrer">requirements</a> before you start with <code>kubeadm</code> installation procedure.</p>

<p>You can also take a look at the general <code>kubeadm</code> installation or runtime <a href="https://kubernetes.io/docs/setup/independent/troubleshooting-kubeadm/" rel="nofollow noreferrer">troubleshooting guide</a>.</p>
