Kubernetes吊舱处于等待状态 [英] Kubernetes pod stuck in waiting state

问题描述

尝试启动此广告连播

apiVersion: v1
kind: Pod
metadata:
  name: tinyproxy
spec:
  containers:
    - name: master
      image: asdrepo.isus.emc.com:8091/francisbesset/tinyproxy
      env:
        - name: MASTER
          value: "true"
      ports:
        - containerPort: 6379
      resources:
        limits:
          cpu: "0.1"
      volumeMounts:
        - mountPath: /tinyproxy-data
          name: data
  volumes:
    - name: data
      emptyDir: {}

这卡在待处理状态.我查看了问题排查指南，但此窗格似乎没有任何事件

This gets stuck in pending state. I looked in the troubleshooting guide, but this pod does not seem to have any events

$ kubectl describe pods tinyproxy
Name:       tinyproxy
Namespace:  default
Node:       /
Labels:     name=tinyproxy
Status:     Pending
IP:
Controllers:    <none>
Containers:
  master:
    Image:  asdrepo.isus.emc.com:8091/francisbesset/tinyproxy
    Port:   6379/TCP
    QoS Tier:
      cpu:  Guaranteed
      memory:   BestEffort
    Limits:
      cpu:  100m
    Requests:
      cpu:  100m
    Environment Variables:
      MASTER:   true
Volumes:
  data:
    Type:   EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
No events.

也

$ kubectl get events
FIRSTSEEN   LASTSEEN   COUNT     NAME                                                    KIND      SUBOBJECT   TYPE      REASON                  SOURCE                                                               MESSAGE
13m         13m        1         10.0.0.5                                                Node                  Normal    Starting                {kubelet 10.0.0.5}                                                   Starting kubelet.
13m         13m        2         10.0.0.5                                                Node                  Warning   MissingClusterDNS       {kubelet 10.0.0.5}                                                   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "kube-proxy-10.0.0.5_kube-system(9fa6e0ea64b9f19ad6996367402408eb)". Falling back to DNSDefault policy.
13m         13m        1         10.0.0.5                                                Node                  Normal    NodeHasSufficientDisk   {kubelet 10.0.0.5}                                                   Node 10.0.0.5 status is now: NodeHasSufficientDisk
13m         13m        1         10.0.0.5                                                Node                  Normal    Starting                {kubelet 10.0.0.5}                                                   Starting kubelet.
13m         13m        1         10.0.0.5                                                Node                  Normal    NodeHasSufficientDisk   {kubelet 10.0.0.5}                                                   Node 10.0.0.5 status is now: NodeHasSufficientDisk
13m         13m        1         k8-dvawxybzux-0-a7m3diiryehx-kube-minion-itahxn4icom6   Node                  Normal    Starting                {kube-proxy k8-dvawxybzux-0-a7m3diiryehx-kube-minion-itahxn4icom6}   Starting kube-proxy.

代理似乎正在运行并且没有重新启动

The proxy does seem to be running and is not restarting

bash-4.3# docker ps
CONTAINER ID        IMAGE                                       COMMAND                  CREATED             STATUS              PORTS               NAMES
d6dd779b301f        gcr.io/google_containers/hyperkube:v1.2.0   "/hyperkube proxy --m"   15 minutes ago      Up 15 minutes                           k8s_kube-proxy.d87e83d4_kube-proxy-10.0.0.5_kube-system_9fa6e0ea64b9f19ad6996367402408eb_caae92ac
8191770f15d9        gcr.io/google_containers/pause:2.0          "/pause"                 15 minutes ago      Up 15 minutes                           k8s_POD.6059dfa2_kube-proxy-10.0.0.5_kube-system_9fa6e0ea64b9f19ad6996367402408eb_e4da5a30

我该如何调试?

推荐答案

看起来调度程序服务未启动(这是在Openstack VM中).所有服务都应该被配置并自动启动.在我手动启动该服务后，此方法起作用.

Looks like the scheduler service did not start (this is in an openstack VM). All services were supposed to be configured and started automatically. This worked after I started the service manually.

这篇关于Kubernetes吊舱处于等待状态的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！