Dashboard Pod status pending

0 votes

My dashboard pod has status "Pending" and if I do a curl call to http://127.0.0.1:8080/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard then I get this result:

"no endpoints available for service \"kubernetes-dashboard\""

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

All pods

core@helena-coreos ~ $ ./kubectl get po --namespace=kube-system
NAME                                     READY     STATUS    RESTARTS   AGE
kube-apiserverd479.185.128.27            1/1       Running   0          5d
kube-apiserver-37.139.31.151             1/1       Running   0          7d
kube-connkkdq-lzmzfdq-kf691.185.128.27   1/1       Running   0          19h
kube-controller-manan-yc59.139.31.151    1/1       Running   0          16h
kube-dns-v11-ika0m                       0/4       Pending   0          19h
kube-proxyd479.185.128.27                1/1       Running   0          5d
kubernetes-dashboard-1775839595-1h0lt    0/1       Pending   0          19h

Describe pod:

core@helena-coreos ~ $ ./kubectl describe pod kubernetes-dashboard-1775839595-1h0lt --namespace="kube-system"
Name:       kubernetes-dashboard-1775839595-1h0lt
Namespace:  kube-system
Node:       /
Labels:     app=kubernetes-dashboard,pod-template-hash=1775839595
Status:     Pending
IP:     
Controllers:    ReplicaSet/kubernetes-dashboard-1775839595
Containers:
  kubernetes-dashboard:
    Image:  gcr.io/google_containers/kubernetes-dashboard-amd64:v1.1.0
    Port:   9090/TCP
    QoS Tier:
      cpu:  BestEffort
      memory:   BestEffort
    Liveness:   http-get http://:9090/ delay=30s timeout=30s period=10s #success=1 #failure=3
    Environment Variables:
Volumes:
  default-token-mn7e9:
    Type:   Secret (a volume populated by a Secret)
    SecretName: default-token-mn7e9
No events.

Service configuration:

core@helena-coreos ~ $ ./kubectl get svc kubernetes-dashboard --namespace=kube-system -o yaml
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: 2016-07-10T22:25:03Z
  labels:
    app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kube-system
  resourceVersion: "58669"
  selfLink: /api/v1/namespaces/kube-system/services/kubernetes-dashboard
  uid: 25d56060-46ed-11e6-9817-040124359901
spec:
  clusterIP: 10.3.0.67
  ports:
  - nodePort: 32014
    port: 80
    protocol: TCP
    targetPort: 9090
  selector:
    app: kubernetes-dashboard
  sessionAffinity: None
  type: NodePort
status:
  loadBalancer: {}

I can’t figure out what the problem is.

Any help is appreciated.

Sep 25, 2018 in Kubernetes by Hannah
• 14,070 points
788 views

1 answer to this question.

0 votes

It’s not able to schedule anything because you don’t have a scheduler.

Set up a scheduler and try the same. For more reference https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/

answered Sep 25, 2018 by Kalgi
• 40,420 points

Related Questions In Kubernetes

0 votes
1 answer

Pod status not ready always - kubernetes

I was having the same issue. In the ...READ MORE

answered Sep 6, 2018 in Kubernetes by Kalgi
• 40,420 points
536 views
0 votes
1 answer

Pod Status containerCreating

I’m not very sure of this error. ...READ MORE

answered Sep 25, 2018 in Kubernetes by Kalgi
• 40,420 points
910 views
0 votes
5 answers
+1 vote
4 answers
+3 votes
1 answer
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
2,067 views
0 votes
3 answers

Kubernetes dashboard status-CrashLoopBackOff

I had the same issue, struggled for days. ...READ MORE

answered Apr 24 in Kubernetes by Bebo
2,223 views
0 votes
2 answers

Pod status terminating-Kubernentes

Delete the finalizers block from resource (pod,deployment,ds ...READ MORE

answered Aug 29, 2018 in Kubernetes by Hannah
• 14,070 points
64 views