<p>I've got a problem with roles and authentication kubernetes. I created a one-node (one maser) cluster, on my baremetal server, and I made this cluster listen on different IP than default (with option &quot;<em>--apiserver-advertise-address=</em> <em>ip address</em> &quot;). But now I basically can do nothing in it, because of <em>kubectl</em> does not work. I can't create pods and services I need. When I created the cluster, without this IP changinh, it works. So my question  is how to fix this? It is probably an authorization problem, but I can't even create cluster role or cluster role binding because of errors like this: <em>&quot; error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User &quot;system:node:e4-1&quot; cannot create resource &quot;clusterrolebindings&quot; in API group &quot;rbac.authorization.k8s.io&quot; at the cluster scope&quot;</em>... Is there any way to &quot;login&quot; as admin, or something, or is there a way to change something in configs files to fix this?</p>

Skyeee
<p>Based on the flag you mention I assume you are using <code>kubeadm</code> to create your cluster. Most probable cause is that you are using the wrong <code>.conf</code> file. My suspicions are that you are using the <code>kubelet.conf</code> instead of <code>admin.conf</code>.</p>
<p>Below you can find an example of the <code>kubeadm init</code> output. It contains steps that you need to follow to start using <code>kubectl</code>:</p>
<pre class="lang-none prettyprint-override"><code>Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

You should now deploy a Pod network to the cluster.
Run &quot;kubectl apply -f [podnetwork].yaml&quot; with one of the options listed at:
  /docs/concepts/cluster-administration/addons/

You can now join any number of machines by running the following on each node
as root:

  kubeadm join &lt;control-plane-host&gt;:&lt;control-plane-port&gt; --token &lt;token&gt; --discovery-token-ca-cert-hash sha256:&lt;hash&gt;
</code></pre>
<p>As you see one of the commands is to copy <code>admin.conf</code> file into <code>/.kube/config</code> which then <code>kubectl</code> uses to manage cluster.</p>
