kubernetes-dashboard not found

[daniel-sherwood]

Hi

I have installed kubernetes-1.0.2-1.9.6 on a DC/OS 0.11 cluster and the Kubernetes Dashboard is not available. The following is returned...

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

I did previously have it working, but after changing a configuration setting (public_nodes) and restarting this issue occured. I have tried re-installing from Kubernetes and even restoring the master node to a snapshot taken before I first did the Kubernetes install and get the same result. I'm guessing this may be to do with which nodes the various kubernetes tasks are allocated to.

Cheers

Daniel Sherwood

[hectorj2f]

@daniel-sherwood Could you share the output of few commands with us to better understand your problem ?
dcos kubernetes plan status deploy
kubectl get nodes
kubectl get pods --all-namespaces

[daniel-sherwood]

[p3061@cuckoo-accessvm-p3061 ~]$ dcos kubernetes plan status deploy
deploy (serial strategy) (IN_PROGRESS)
├─ etcd (serial strategy) (COMPLETE)
│  └─ etcd-0:[peer] (COMPLETE)
├─ apiserver (parallel strategy) (COMPLETE)
│  └─ kube-apiserver-0:[instance] (COMPLETE)
├─ kubernetes-api-proxy (parallel strategy) (COMPLETE)
│  └─ kubernetes-api-proxy-0:[install] (COMPLETE)
├─ controller-manager (parallel strategy) (COMPLETE)
│  └─ kube-controller-manager-0:[instance] (COMPLETE)
├─ scheduler (parallel strategy) (COMPLETE)
│  └─ kube-scheduler-0:[instance] (COMPLETE)
├─ node (parallel strategy) (STARTING)
│  ├─ kube-node-0:[kube-proxy] (STARTING)
│  ├─ kube-node-0:[coredns] (STARTING)
│  └─ kube-node-0:[kubelet] (STARTING)
├─ public-node (parallel strategy) (COMPLETE)
└─ mandatory-addons (serial strategy) (PENDING)
   ├─ mandatory-addons-0:[kube-dns] (PENDING)
   ├─ mandatory-addons-0:[metrics-server] (PENDING)
   ├─ mandatory-addons-0:[dashboard] (PENDING)
   └─ mandatory-addons-0:[ark] (PENDING)
[p3061@cuckoo-accessvm-p3061 ~]$ kubectl get nodes
the server doesn't have a resource type "nodes"
[p3061@cuckoo-accessvm-p3061 ~]$ kubectl get pods --all-namespaces
the server doesn't have a resource type "pods"

I notice the various PENDING items and have stopped various other services and allocated additional CPUs to ensure there are adequate resources and it still shows kube-dns cycling through PENDING/STARTING/STARTED.

Cheers

[hectorj2f]

@daniel-sherwood Based on what you shared, it seems there are not enough resources to schedule the single kube-node you have. As you can guess, you don't have any kube-node therefore the mandatory pods cannot be deployed. Could you try to uninstall and install again the framework? Also, it'd be interesting to see which resources you already have allocated with https://<CLUSTER_IP>/mesos/#/agents

[daniel-sherwood]

Just went to get that information and all the bits now seem to be deployed and the dashboard is available.

deploy (serial strategy) (COMPLETE)
├─ etcd (serial strategy) (COMPLETE)
│  └─ etcd-0:[peer] (COMPLETE)
├─ apiserver (parallel strategy) (COMPLETE)
│  └─ kube-apiserver-0:[instance] (COMPLETE)
├─ kubernetes-api-proxy (parallel strategy) (COMPLETE)
│  └─ kubernetes-api-proxy-0:[install] (COMPLETE)
├─ controller-manager (parallel strategy) (COMPLETE)
│  └─ kube-controller-manager-0:[instance] (COMPLETE)
├─ scheduler (parallel strategy) (COMPLETE)
│  └─ kube-scheduler-0:[instance] (COMPLETE)
├─ node (parallel strategy) (COMPLETE)
│  ├─ kube-node-0:[kube-proxy] (COMPLETE)
│  ├─ kube-node-0:[coredns] (COMPLETE)
│  └─ kube-node-0:[kubelet] (COMPLETE)
├─ public-node (parallel strategy) (COMPLETE)
└─ mandatory-addons (serial strategy) (COMPLETE)
   ├─ mandatory-addons-0:[kube-dns] (COMPLETE)
   ├─ mandatory-addons-0:[metrics-server] (COMPLETE)
   ├─ mandatory-addons-0:[dashboard] (COMPLETE)
   └─ mandatory-addons-0:[ark] (COMPLETE)

Thanks for the help.

[hbceylan]

Hi, I have installed but still dashboard not available?

➜  ~ dcos kubernetes plan status deploy
deploy (serial strategy) (COMPLETE)
├─ etcd (serial strategy) (COMPLETE)
│  └─ etcd-0:[peer] (COMPLETE)
├─ apiserver (parallel strategy) (COMPLETE)
│  └─ kube-apiserver-0:[instance] (COMPLETE)
├─ mandatory-addons (serial strategy) (COMPLETE)
│  ├─ mandatory-addons-0:[additional-cluster-role-bindings] (COMPLETE)
│  ├─ mandatory-addons-0:[kube-dns] (COMPLETE)
│  ├─ mandatory-addons-0:[metrics-server] (COMPLETE)
│  ├─ mandatory-addons-0:[dashboard] (COMPLETE)
│  └─ mandatory-addons-0:[ark] (COMPLETE)
├─ kubernetes-api-proxy (parallel strategy) (COMPLETE)
│  └─ kubernetes-api-proxy-0:[install] (COMPLETE)
├─ controller-manager (parallel strategy) (COMPLETE)
│  └─ kube-controller-manager-0:[instance] (COMPLETE)
├─ scheduler (parallel strategy) (COMPLETE)
│  └─ kube-scheduler-0:[instance] (COMPLETE)
├─ node (parallel strategy) (COMPLETE)
│  └─ kube-node-0:[kube-proxy, coredns, kubelet] (COMPLETE)
└─ public-node (parallel strategy) (COMPLETE)

[pires]

If you're reading this far, @hbceylan as deployed the new (as I write this) release, 1.1.0-1.10.3, which had a breaking change on how we expose the API and, thefore, the dashboard.