Question

我已经在互联网上寻找解决方案，但找不到任何有用的方法。我有一个服务器主机，该主机运行Ubuntu 18.04。 Pod始终处于待处理状态，不想运行。

NAMESPACE            NAME                                                  READY   STATUS    RESTARTS   AGE
container-registry   pod/registry-7cf58dcdcc-hf8gx                         0/1     Pending   0          12m
kube-system          pod/coredns-588fd544bf-4m6mj                          0/1     Pending   0          12m
kube-system          pod/dashboard-metrics-scraper-db65b9c6f-gj5x4         0/1     Pending   0          12m
kube-system          pod/heapster-v1.5.2-58fdbb6f4d-q6plc                  0/4     Pending   0          12m
kube-system          pod/hostpath-provisioner-75fdc8fccd-6mdvc             0/1     Pending   0          12m
kube-system          pod/kubernetes-dashboard-67765b55f5-8xsh5             0/1     Pending   0          12m
kube-system          pod/monitoring-influxdb-grafana-v4-6dc675bf8c-82fg4   0/2     Pending   0          12m

当我输入mickrok8s.kubectl describe nodes时，我将得到此输出...

 Normal   Starting                 15s    kubelet, h2860142.stratoserver.net     Starting kubelet.
  Warning  InvalidDiskCapacity      15s    kubelet, h2860142.stratoserver.net     invalid capacity 0 on image filesystem
  Normal   NodeHasSufficientPID     15s    kubelet, h2860142.stratoserver.net     Node h2860142.stratoserver.net status is now: NodeHasSufficientPID
  Normal   NodeHasNoDiskPressure    15s    kubelet, h2860142.stratoserver.net     Node h2860142.stratoserver.net status is now: NodeHasNoDiskPressure
  Normal   NodeHasSufficientMemory  15s    kubelet, h2860142.stratoserver.net     Node h2860142.stratoserver.net status is now: NodeHasSufficientMemory
  Normal   NodeHasSufficientPID     3s     kubelet, h2860142.stratoserver.net     Node h2860142.stratoserver.net status is now: NodeHasSufficientPID

“ microk8s.kubectl获取节点-o宽”的输出...

NAME                        STATUS     ROLES    AGE   VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION   CONTAINER-RUNTIME
h2860142.stratoserver.net   NotReady   <none>   23h   v1.18.3   85.214.165.16   <none>        Ubuntu 18.04.4 LTS   4.15.0           containerd://1.2.5

microk8s.kubectl get pods -A

的输出

NAMESPACE            NAME                                              READY   STATUS    RESTARTS   AGE
container-registry   registry-7cf58dcdcc-hf8gx                         0/1     Pending   0          63m
kube-system          coredns-588fd544bf-4m6mj                          0/1     Pending   0          63m
kube-system          dashboard-metrics-scraper-db65b9c6f-gj5x4         0/1     Pending   0          63m
kube-system          heapster-v1.5.2-58fdbb6f4d-q6plc                  0/4     Pending   0          63m
kube-system          hostpath-provisioner-75fdc8fccd-6mdvc             0/1     Pending   0          63m
kube-system          kubernetes-dashboard-67765b55f5-8xsh5             0/1     Pending   0          63m
kube-system          monitoring-influxdb-grafana-v4-6dc675bf8c-82fg4   0/2     Pending   0          63m

“ microk8s.inspect”的输出

Inspecting Certificates                                                                
Inspecting services                                                                    
  Service snap.microk8s.daemon-cluster-agent is running                                
  Service snap.microk8s.daemon-flanneld is running                                     
  Service snap.microk8s.daemon-containerd is running                                   
  Service snap.microk8s.daemon-apiserver is running                                    
  Service snap.microk8s.daemon-apiserver-kicker is running                             
  Service snap.microk8s.daemon-proxy is running                                        
  Service snap.microk8s.daemon-kubelet is running                                      
  Service snap.microk8s.daemon-scheduler is running                                    
  Service snap.microk8s.daemon-controller-manager is running                           
  Service snap.microk8s.daemon-etcd is running                                         
  Copy service arguments to the final report tarball                                   
Inspecting AppArmor configuration                                                      
Gathering system information                                                           
  Copy processes list to the final report tarball                                      
  Copy snap list to the final report tarball                                           
  Copy VM name (or none) to the final report tarball                                   
  Copy disk usage information to the final report tarball                              
  Copy memory usage information to the final report tarball                            
  Copy server uptime to the final report tarball                                       
  Copy current linux distribution to the final report tarball                          
  Copy openSSL information to the final report tarball                                 
  Copy network configuration to the final report tarball                               
Inspecting kubernetes cluster                                                          
  Inspect kubernetes cluster                                                           

Building the report tarball                                                            
  Report tarball is at /var/snap/microk8s/1422/inspection-report-20200609_120308.tar.gz

那我该如何解决这个问题？

谢谢：）

Answer 1

the docs 中有一节是关于此的。

<块引用>

如果 Pod 卡在 Pending 状态，则意味着它无法调度到节点上。通常，这是因为一种或另一种类型的资源不足而阻止了调度。查看kubectl describe的输出...

就我而言，kubectl describe pods <podname> 说：

Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  6m1s (x3 over 7m6s)  default-scheduler  0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.

搜索那个警告给了我我需要的东西。幸运的是，那里也可能会显示有用的警告。

Microk8s Pod在Ubuntu上处于待处理状态

1 个答案: