The problem is very much what the error says. When you generate the cert for the apiserver, you need to specify the name by which you will be accessing the site. In this case, kube.beta.mydomain.com.
On Fri, Jun 10, 2016 at 10:50 AM Gary Denner <[email protected]> wrote: > Folks > > Any idea how to fix this, we are running this script > > https://coreos.com/kubernetes/docs/latest/kubernetes-on-aws.html > > And all looks good, it provisions the stuff in AWS, sets up the security > groups and all is good (so you think) > > then you run sudo /usr/local/bin/kubectl --kubeconfig=kubeconfig get nodes > and it returns with Unable to connect to the server: x509: certificate is > valid for kubernetes, kubernetes.default, kubernetes.default.svc, > kubernetes.default.svc.cluster.local, kube-prod-dns, not > kube.beta.mydomain.com? > > Any help much appreciated. > > > > -- Seán C McCord CyCore Systems, Inc +1 888 240 0308
