Only if you actually _have_ nodes running and communicating. Are all of your kubelets running and populated with their respective TLS assets? If they (the kubelets) are running, take a look at one of their logs (journalctl -u kubelet) and see if you can tell what is failing.
On Fri, Jun 10, 2016 at 12:57 PM Gary Denner <[email protected]> wrote: > OK now when I run sudo /usr/local/bin/kubectl --kubeconfig=kubeconfig get > nodes it returns nothing, I would have expected some list of nodes right? > > On Friday, June 10, 2016 at 3:50:32 PM UTC+1, Gary Denner 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
