<p>I was having issues with <code>kubeadm init</code>, and so i ran <code>kubeadm reset</code> and then <code>kubeadm init</code> and the problem at hand went away, but now I have another problem and that is that when I run <code>kubectl get all</code>, I get the following response:</p>

<pre><code>NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 &lt;none&gt; 443/TCP 3h6m
Error from server (Forbidden): replicationcontrollers is forbidden: User "system:node:abc-server.localdomain" cannot list resource "replicationcontrollers" in API group "" in the namespace "default"
Error from server (Forbidden): daemonsets.apps is forbidden: User "system:node:abc-server.localdomain" cannot list resource "daemonsets" in API group "apps" in the namespace "default"
Error from server (Forbidden): deployments.apps is forbidden: User "system:node:abc-server.localdomain" cannot list resource "deployments" in API group "apps" in the namespace "default"
Error from server (Forbidden): replicasets.apps is forbidden: User "system:node:abc-server.localdomain" cannot list resource "replicasets" in API group "apps" in the namespace "default"
Error from server (Forbidden): statefulsets.apps is forbidden: User "system:node:abc-server.localdomain" cannot list resource "statefulsets" in API group "apps" in the namespace "default"
Error from server (Forbidden): horizontalpodautoscalers.autoscaling is forbidden: User "system:node:abc-server.localdomain" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "default"
Error from server (Forbidden): jobs.batch is forbidden: User "system:node:abc-server.localdomain" cannot list resource "jobs" in API group "batch" in the namespace "default"
Error from server (Forbidden): cronjobs.batch is forbidden: User "system:node:abc-server.localdomain" cannot list resource "cronjobs" in API group "batch" in the namespace "default"
</code></pre>

<p>I've exhausted my googling abilities with my limited kubernetes vocabulary, so hoping someone here could help me with the following:</p>

<ol>
<li>what's happening?!  (is this a RBAC Authorization issue?)</li>
<li>how can i resolve this?  as this is a dev environment that will definitely require some clean up, I don't mind a quick and dirty way just so i can continue with the task at hand (which is to just get things up and running again)</li>
</ol>

Handsome Wayfarer
<p>As @Software Engineer mentioned in his comment there is a <a href="https://github.com/kubernetes/kubeadm/issues/1721" rel="nofollow noreferrer">github</a> issue with a fix for that:</p>

<p>User <a href="https://github.com/kubernetes/kubeadm/issues/1721#issuecomment-520437689" rel="nofollow noreferrer">neolit123</a> on github posted this solution:</p>

<blockquote>
  <p>getting a permission error during pod network setup, means you are trying to  <code>kubectl apply</code>  manifest files using a kubeconfig file which does not have the correct permissions.</p>
  
  <p>make sure that your  <code>/etc/kubernetes/admin.conf</code>  is generated by kubeadm and contains  <code>kubernetes-admin</code>  as the user.</p>

<pre><code>root@master:~# kubectl auth can-i create deploy
</code></pre>
  
  <p>which kubeconfig is this command using?<br>
  try</p>

<pre><code>root@master:~# KUBECONFIG=/etc/kubernetes/admin.conf kubectl auth can-i create deploy

</code></pre>
  
  <blockquote>
    <p>I wanted to check the release notes, but there is no much information, or I don't know interpret it. Does anyone have any information about what are the changes, or what am I doing wrong?</p>
  </blockquote>
  
  <p>AFAIK, there is no such change that breaks this between 1.14.4 and .3.</p>
</blockquote>
