Kubernetes仪表板-ServiceUnavailable(503错误) [英] Kubernetes dashboard - ServiceUnavailable (503 error)

查看:588
本文介绍了Kubernetes仪表板-ServiceUnavailable(503错误)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是Kubernetes的新手.我正在尝试使用kops在AWS上设置Kubernetes集群.我可以成功设置群集.但是,我无法访问仪表板UI. ( https://kubernetes .io/docs/tasks/access-application-cluster/web-ui-dashboard/#accessing-the-dashboard-ui )

I am a Kubernetes newbie. I am trying to setup a Kubernetes cluster on AWS using kops. I was successfully able to setup the cluster. However, I am not able to access the Dashboard UI. (https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/#accessing-the-dashboard-ui)

当我访问主节点时,看到以下错误:

When I access the master node, I see the following error:

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

我看到仪表板的状态为CrashLoopBackOff. (请注意:我在以下日志中删除了其他Pod的名称)

I see the status of the dashboard as CrashLoopBackOff. (Please note: I have removed the names of the other pods in the following log)

~$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                                    READY     STATUS             RESTARTS   AGE
kube-system   kubernetes-dashboard-4167803980-vnx3k                   0/1       CrashLoopBackOff   6          6m

$ kubectl logs kubernetes-dashboard-4167803980-vnx3k --namespace=kube-system
2017/09/25 17:50:37 Using in-cluster config to connect to apiserver
2017/09/25 17:50:37 Using service account token for csrf signing
2017/09/25 17:50:37 No request provided. Skipping authorization
2017/09/25 17:50:37 Starting overwatch
2017/09/25 17:50:37 Successful initial request to the apiserver, version: v1.7.2
2017/09/25 17:50:37 New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Starting
2017/09/25 17:50:37 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-system
2017/09/25 17:50:37 Initializing secret synchronizer synchronously using secret kubernetes-dashboard-key-holder from namespace kube-system
2017/09/25 17:50:37 Initializing JWE encryption key from synchronized object
2017/09/25 17:50:37 Creating in-cluster Heapster client
2017/09/25 17:50:37 Serving securely on HTTPS port: 8443
2017/09/25 17:50:37 open /certs/dashboard.crt: no such file or directory

对于使仪表板运行的任何帮助/建议,我将表示由衷的感谢.预先感谢!

I would sincerely appreciate any help/suggestions to get the dashboard running. Thanks in advance!

推荐答案

您使用的是最新的仪表板,看起来它需要SSL证书.尝试使用1.6.3,它将在没有SSL证书的情况下工作.

Your using latest dashboard, looks like it required SSL certificate. try with 1.6.3 it will work with-out SSL cert.

我正在集群中运行此版本.

I am running this version in my cluster.

kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml

头盔命令以安装仪表板

kubectl create clusterrolebinding add-on-cluster-admin --clusterrole=cluster-admin  --serviceaccount=kube-system:default
helm install stable/kubernetes-dashboard  --name kubernetes-dashboard --namespace  kube-system --debug
helm install stable/heapster  --namespace  kube-system

这篇关于Kubernetes仪表板-ServiceUnavailable(503错误)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆