<p>I have one successfully working cluster, with out any problems, I've tried to make a copy of it. It's working basically, except one issue - token generated by apiserver is not valid with error message:</p>

<pre><code>6 handlers.go:37] Unable to authenticate the request due to an error: crypto/rsa: verification error
</code></pre>

<p>I have api server started up with following parameters:</p>

<pre><code>kube-apiserver --address=0.0.0.0    --admission_control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota --service-cluster-ip-range=10.116.0.0/23 --client_ca_file=/srv/kubernetes/ca.crt --basic_auth_file=/srv/kubernetes/basic_auth.csv --authorization-mode=AlwaysAllow  --tls_cert_file=/srv/kubernetes/server.cert --tls_private_key_file=/srv/kubernetes/server.key --secure_port=6443 --token_auth_file=/srv/kubernetes/known_tokens.csv  --v=2 --cors_allowed_origins=.* --etcd-config=/etc/kubernetes/etcd.config --allow_privileged=False
</code></pre>

<p>I think I'm missing something but can't find what exactly, any help will be appreciated! </p>

<p>So, apparently it was wrong server.key used by controller manager. 
According to <a href="http://kubernetes.io/v1.0/docs/admin/service-accounts-admin.html" rel="nofollow">kubernetes documentation</a> token is generated by controller manager. </p>

<p>While I was doing copy of the all my configuration, I had to change ipaddress and had to change certificate due to this as well. But controller-manager started with "old" certificate and after the change created wrong keys because server.key. </p>
