I am creating kubernetes 1.4 cluster and want to access the dashboard once cluster is created. I am deploying cluster on VMs created using apache cloudstack platform. I am using CoreOS for creating the cluster.

However currently I am facing inconsistency of dashboard service access issue.

Sometimes in the same network with exactly same environment when cluster is created a fresh dashboard comes up easily without any issues.

However if I create cluster again in the same environment again (of course by removing the existing cluster) there is no guarantee that dashboard will come up. What I observed is I just cant guarantee if I create the cluster dashboard may come or may not come on exactly the same environment.

When dashboard is not coming up these are the responses I get in browser:

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "no endpoints available for service \"kubernetes-dashboard\"",
  "reason": "ServiceUnavailable",
  "code": 503
}

OR this response:

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "endpoints \"kubernetes-dashboard\" not found",
  "reason": "NotFound",
  "details": {
    "name": "kubernetes-dashboard",
    "kind": "endpoints"
  },
  "code": 404
}

I am not able to get root cause of this issue.

When dashboard is not coming, I checked services running on master. Usually all the services are running except dashboard service: kube-apiserver, kube-controller-manager and kube-scheduler.

Ideally when I run the command kubectl get pods --all-namespaces I should see the dashboard container up and running, but it doesn't get listed.

Here are version details I am using:

Kubernetes api-server version - 1.4.0

client version - 1.4.0

Dashboard service version - gcr.io/google_containers/kubernetes-dashboard-amd64:v1.5.0

Dashboard yaml is downloaded from

CoreOS Version - 1010.5.0

Any help/hint in this regard greatly appreciated.

Thanks so much in advance.

-picku