首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >Kubernetes仪表板不工作

Kubernetes仪表板不工作
EN

Stack Overflow用户
提问于 2016-12-22 21:36:29
回答 2查看 2.4K关注 0票数 0

我试图实现kubernetes仪表板,但它一直处于CrashLoopBackoff状态,无论我部署它多少次,它都具有相同的信念

代码语言:javascript
复制
host-xxx:~ # kubectl get pods --all-namespaces                                                                                                                                                                                          
NAMESPACE     NAME                                    READY     STATUS             RESTARTS   AGE
default       locust-master-pr59t                     1/1       Running            0          2d
default       my-nginx-2565190728-8z0eh               1/1       Running            0          2d
default       my-nginx-2565190728-if4my               1/1       Running            0          2d
kube-system   kubernetes-dashboard-1975554030-80rxv   0/1       CrashLoopBackOff   249        21h

我有来自"kubectl create -f https://rawgit.com/kubernetes/dashboard/master/src/deploy/kubernetes-dashboard-head.yaml“的yaml文件。

代码语言:javascript
复制
host-xxx:~ # kubectl describe pod --namespace=kube-system kubernetes-dashboard-1975554030-80rxv
Name:           kubernetes-dashboard-1975554030-80rxv
Namespace:      kube-system
Node:           host-44-11-1-25/44.11.1.25
Start Time:     Wed, 21 Dec 2016 14:49:48 +0000
Labels:         app=kubernetes-dashboard
                pod-template-hash=1975554030
Status:         Running
IP:             172.20.140.2
Controllers:    ReplicaSet/kubernetes-dashboard-1975554030
Containers:
  kubernetes-dashboard:
    Container ID:               docker://708aac5cebdff057b69cec94e582cb45f7dba424c336fb320dd0d5e3243fc323
    Image:                      gcr.io/google_containers/kubernetes-dashboard-amd64:v1.5.0
    Image ID:                   docker://sha256:e5133bac8024ac6c916f16df8790259b5504a800766bee87dcf90ec7d634a418
    Port:                       9090/TCP
    State:                      Waiting
      Reason:                   CrashLoopBackOff
    Last State:                 Terminated
      Reason:                   Error
      Exit Code:                1
      Started:                  Thu, 22 Dec 2016 11:32:12 +0000
      Finished:                 Thu, 22 Dec 2016 11:32:13 +0000
    Ready:                      False
    Restart Count:              244
    Liveness:                   http-get http://:9090/ delay=30s timeout=30s period=10s #success=1 #failure=3
    Environment Variables:      <none>
Conditions:
  Type          Status
  Initialized   True 
  Ready         False 
  PodScheduled  True 
No volumes.
QoS Tier:       BestEffort
Events:
  FirstSeen     LastSeen        Count   From                            SubobjectPath                           Type            Reason                  Message
  ---------     --------        -----   ----                            -------------                           --------        ------                  -------
  20h           3m              245     {kubelet host-44-11-1-25}       spec.containers{kubernetes-dashboard}   Normal          Pulling                 pulling image "gcr.io/google_containers/kubernetes-dashboard-amd64:v1.5.0"
  20h           3m              246     {kubelet host-44-11-1-25}                                               Warning         MissingClusterDNS       kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to DNSDefault policy.
  20h           3m              245     {kubelet host-44-11-1-25}       spec.containers{kubernetes-dashboard}   Normal          Pulled                  Successfully pulled image "gcr.io/google_containers/kubernetes-dashboard-amd64:v1.5.0"
  20h           3m              236     {kubelet host-44-11-1-25}       spec.containers{kubernetes-dashboard}   Normal          Created                 (events with common reason combined)
  20h           3m              236     {kubelet host-44-11-1-25}       spec.containers{kubernetes-dashboard}   Normal          Started                 (events with common reason combined)
  20h           3s              5940    {kubelet host-44-11-1-25}       spec.containers{kubernetes-dashboard}   Warning         BackOff                 Back-off restarting failed docker container
  20h           3s              5906    {kubelet host-44-11-1-25}                                               Warning         FailedSync              Error syncing pod, skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-1975554030-80rxv_kube-system(b893d9c4-c78c-11e6-bd87-fa163e39bb70)"

我不确定为什么我会有这个错误信息,在minion上,它看起来像是图像被拉出,我可以用docker拉它。

你们有关于这个的理论吗?

EN

回答 2

Stack Overflow用户

发布于 2016-12-30 19:16:17

镜像拉取成功,POD中容器启动失败,在此阶段可以查看容器日志校验问题:

kubectl logs --namespace=kube-system kubernetes-dashboard-1975554030-80rxv

库贝莱特发出了警告:

kubelet没有配置ClusterDNS IP,无法使用ClusterFirst策略创建实例。回退到DNSDefault策略。

也许问题与DNS有关,我有一个自定义安装,其中仪表板容器仅在DNS处于活动状态时启动,请验证日志以了解它失败的原因。

票数 1
EN

Stack Overflow用户

发布于 2017-10-26 10:46:21

就像前面的答案说的那样,

您可以使用命令kubectl logs --namespace=kube-system kubernetes-dashboard-1975554030-80rxv来检查所发生的错误的详细信息。

对于错误kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to DNSDefault policy.

可能您还没有启用kubedns组件,这可能会导致此问题。

如果您仍在使用https://rawgit.com/kubernetes/dashboard/master/src/deploy/kubernetes-dashboard-head.yaml创建kubernetes仪表板,则可以运行kubectl edit pod kubernetes-dashboard-1975554030-80rxv -n kube-system命令,手动将DNS策略更改为默认值。关键字应该是spec.template.spec.dnsPolicy to Default,然后重新创建此Pod,看看它是否可以工作。

有关更多细节,请访问http://blog.kubernetes.io/2017/04/configuring-private-dns-zones-upstream-nameservers-kubernetes.html

顺便说一句,您还可以使用官方仪表板来创建https://github.com/kubernetes/dashboard#getting-started

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/41284447

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档