<p>Following <a href="https://upcloud.com/community/tutorials/install-kubernetes-cluster-centos-8" rel="noreferrer">this tutorial</a>, I set up a worker node for my cluster. However, after running the <code>join</code> command and attempting <code>kubectl get node</code> to verify the node was connected, I am met with the following error</p>
<pre><code>W0215 17:58:44.648813 3084402 loader.go:223] Config not found: /etc/kubernetes/admin.conf
The connection to the server localhost:8080 was refused - did you specify the right host or port?
</code></pre>
<p>Checking for the existence of <code>admin.conf</code> in <code>/etc/kubernetes/</code> shows it does not exist. I have ensured that <code>$HOME/.kube/config</code> is also clear. Why is the join command not creating an admin.conf file?</p>

arshbot
<p><strong>TLDR</strong></p>
<ol>
<li>Run <code>join</code> with sudo</li>
<li><code> mv /etc/kubernetes/kubelet.conf /etc/kubernetes/admin.conf</code></li>
</ol>
<hr />
<p>After some tinkering, I realized it was a combination of a permissions error and the correct file being generated with an incorrect name.</p>
<p>Instead of running <code>kubeadm join ...</code> naked, running with sudo allowed for the command to create files necessary in <code>/etc/kubernetes</code></p>
<pre><code>sudo kubeadm join &lt;MASTER_IP:PORT&gt; --token &lt;TOKEN&gt;     --discovery-token-ca-cert-hash &lt;HASH&gt;
</code></pre>
<p>However this doesn't generate an <code>admin.conf</code>, but does create a <code>kubelet.conf</code>. I'm unsure why this happens, and couldn't find any documentation on this behavior, however running <code>kubectl</code> with the following parameter solved my issue</p>
<pre><code>kubectl get nodes --kubeconfig /etc/kubernetes/kubelet.conf
</code></pre>
<p>Rename <code>kubelet.conf</code> to <code>admin.conf</code> for your convenience at this point.</p>
