2016-12-22 111 views
0

我試圖實現kubernetes儀表板,但所有它在CrashLoopBackoff狀態,並不要緊,我多少次部署有同樣的信念Kubernetes儀表不能正常工作

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 

我有YAML時間從「kubectl創建-f https://rawgit.com/kubernetes/dashboard/master/src/deploy/kubernetes-dashboard-head.yaml

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)" 

我n要知道爲什麼我有這樣的錯誤消息,在僕從看起來像拉,我可以與搬運工人把它..

文件3210

你們有這方面的理論嗎?

回答

1

圖像成功扳回一和容器未能在POD開始,在這個舞臺上,你可以檢查出來的問題,檢驗容器的日誌:

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

的kubelet發出警告:

kubelet沒有配置ClusterDNS IP,並且無法使用「ClusterFirst」策略創建Pod。回落到DNSDefault策略。

也許問題與DNS有關,我有一個自定義安裝,儀表板容器只在DNS活動時啓動,驗證日誌以瞭解它爲什麼失敗。

0

就像早期的回答說,

你可以使用命令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.dnsPolicyDefault然後重新創建此Pod以查看它是否可行。

更多細節可以在http://blog.kubernetes.io/2017/04/configuring-private-dns-zones-upstream-nameservers-kubernetes.html

發現順便說一句,你還可以使用官方的儀表板創建https://github.com/kubernetes/dashboard#getting-started