<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>

prashant.kr.mod
<p>I have found my solution for this. I was having issue running kubernetes cluster because the kubernetes components are distributed on multiple servers. Once I created the master node and slave(worker) node on the same machine, the issue got resolved.<br>
The steps that I took to resolve the issue:<br>
1. on slave/worker machine, run this command: kubeadm reset<br>
2. on master node, generate the token by running this command: kubeadm generate token.<br>
3. use the token generated in master machine on the slave node, so that the node machine can join the kubernetes cluster.</p>

<p>Cheers!!</p>
