<p>I followed this guide <a href="https://coreos.com/kubernetes/docs/latest/kubernetes-on-aws-launch.html" rel="nofollow noreferrer">https://coreos.com/kubernetes/docs/latest/kubernetes-on-aws-launch.html</a> to create a kubernetes cluster on AWS with <a href="https://github.com/coreos/kube-aws" rel="nofollow noreferrer"><code>kube-aws</code></a>.</p>

<p>I am using <code>kube-aws</code> to <code>v0.9.4-rc2</code></p>

<p>After successfully do <code>kube-aws up --s3-uri s3://..</code>, I tried to get the nodes with <code>kubectl get nodes</code>, and that's when I get this error:</p>

<pre><code>:; kubectl get nodes
Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
</code></pre>

<p>In the <code>kubeconfig</code> file, there is a line describing the certificate authority:</p>

<pre><code>apiVersion: v1
kind: Config
clusters:
- cluster:
    certificate-authority: credentials/ca.pem
</code></pre>

<p>Does anyone know what might have gone wrong for me? How could I debug it a bit further?</p>

<p>It seems like the problem was because my credentials were not all generated correctly. So perhaps the apiserver cert was signed with a wrong ca cert? Not sure how that might've happened.</p>

<p>Anyway, deleting the <code>credentials</code> directory, then destroy the cluster and bring it up again solved the problem for me. Luckily it's still an experimental cluster, so I could do that. Not sure if I could've fixed it without destroying the cluster.</p>
