【K8S】READY:0/1 STATUS:Pending 获取POD状态异常

于 2024-07-20 22:22:04 发布
阅读量41 收藏
点赞数
分类专栏： 容器云平台-Kubernete运维 文章标签： kubernetes docker 容器
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_43346403/article/details/140578631
版权

1.calico 网络失败

kubectl get pod --all-namespaces -o wide
NAMESPACE     NAME                                       READY   STATUS     RESTARTS   AGE   IP             NODE     NOMINATED NODE   READINESS GATES
kube-system   calico-kube-controllers-554647c955-8sxdh   0/1     Pending    0          4m    <none>         <none>   <none>           <none>
kube-system   calico-node-6mqkf                          0/1     Init:0/2   0          4m    192.168.1.15   k8s4     <none>           <none>
kube-system   calico-node-7bhwx                          0/1     Init:0/2   0          4m    192.168.1.17   k8s6     <none>           <none>
kube-system   calico-node-llwt6                          0/1     Init:0/2   0          4m    192.168.1.12   k8s1     <none>           <none>
kube-system   calico-node-mcb4c                          0/1     Init:0/2   0          4m    192.168.1.16   k8s5     <none>           <none>
kube-system   calico-node-mkdwr                          0/1     Init:0/2   0          4m    192.168.1.14   k8s3     <none>           <none>
kube-system   calico-node-xn2jz                          0/1     Init:0/2   0          4m    192.168.1.13   k8s2     <none>           <none>
kube-system   calico-typha-6454f6cfd7-j7729              0/1     Pending    0          4m    <none>         <none>   <none>           <none>

[root@K8S1 work]# kubectl get pod -A
NAMESPACE     NAME                                       READY   STATUS     RESTARTS   AGE
kube-system   calico-kube-controllers-554647c955-p7bjc   0/1     Pending    0          4m36s
kube-system   calico-node-j7825                          0/1     Init:0/2   0          4m36s
kube-system   calico-node-ktmf5                          0/1     Init:0/2   0          4m36s
kube-system   calico-node-nf5wg                          0/1     Init:0/2   0          4m36s
kube-system   calico-node-rwpfq                          0/1     Init:0/2   0          4m36s
kube-system   calico-node-scm7s                          0/1     Init:0/2   0          4m36s
kube-system   calico-node-tpqbl                          0/1     Init:0/2   0          4m36s
kube-system   calico-typha-6454f6cfd7-z5bvk              0/1     Pending    0          4m36s

 2.查看状态 

 [root@K8S1 work]# kubectl describe pods calico-node-rwpfq --namespace kube-system 
Name:                 calico-node-rwpfq
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 k8s3/192.168.1.14
Start Time:           Sat, 20 Jul 2024 21:58:45 +0800
Labels:               controller-revision-hash=6cdbc66bf4
                      k8s-app=calico-node
                      pod-template-generation=1
Annotations:          <none>
Status:               Pending
IP:                   192.168.1.14
IPs:
  IP:           192.168.1.14
Controlled By:  DaemonSet/calico-node
Init Containers:
  upgrade-ipam:
    Container ID:  
    Image:         192.168.1.11:443/myharbor/cni:v3.22.0
    Image ID:      
    Port:          <none>
    Host Port:     <none>
    Command:
      /opt/cni/bin/calico-ipam
      -upgrade
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Environment Variables from:
      kubernetes-services-endpoint  ConfigMap  Optional: true
    Environment:
      KUBERNETES_NODE_NAME:        (v1:spec.nodeName)
      CALICO_NETWORKING_BACKEND:  <set to the key 'calico_backend' of config map 'calico-config'>  Optional: false
    Mounts:
      /host/opt/cni/bin from cni-bin-dir (rw)
      /var/lib/cni/networks from host-local-net-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-54hkd (ro)
  install-cni:
    Container ID:  
    Image:         192.168.1.11:443/myharbor/cni:v3.22.0
    Image ID:      
    Port:          <none>
    Host Port:     <none>
    Command:
      /opt/cni/bin/install
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Environment Variables from:
      kubernetes-services-endpoint  ConfigMap  Optional: true
    Environment:
      CNI_CONF_NAME:         10-calico.conflist
      CNI_NETWORK_CONFIG:    <set to the key 'cni_network_config' of config map 'calico-config'>  Optional: false
      KUBERNETES_NODE_NAME:   (v1:spec.nodeName)
      CNI_MTU:               <set to the key 'veth_mtu' of config map 'calico-config'>  Optional: false
      SLEEP:                 false
    Mounts:
      /host/etc/cni/net.d from cni-net-dir (rw)
      /host/opt/cni/bin from cni-bin-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-54hkd (ro)
Containers:
  calico-node:
    Container ID:   
    Image:          192.168.1.11:443/myharbor/node:v3.22.0
    Image ID:       
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Requests:
      cpu:      250m
    Liveness:   exec [/bin/calico-node -felix-live -bird-live] delay=10s timeout=10s period=10s #success=1 #failure=6
    Readiness:  exec [/bin/calico-node -felix-ready -bird-ready] delay=0s timeout=10s period=10s #success=1 #failure=3
    Environment Variables from:
      kubernetes-services-endpoint  ConfigMap  Optional: true
    Environment:
      DATASTORE_TYPE:                     kubernetes
      FELIX_TYPHAK8SSERVICENAME:          <set to the key 'typha_service_name' of config map 'calico-config'>  Optional: false
      WAIT_FOR_DATASTORE:                 true
      NODENAME:                            (v1:spec.nodeName)
      CALICO_NETWORKING_BACKEND:          <set to the key 'calico_backend' of config map 'calico-config'>  Optional: false
      CLUSTER_TYPE:                       k8s,bgp
      IP_AUTODETECTION_METHOD:            interface=ens.*
      IP:                                 autodetect
      CALICO_IPV4POOL_IPIP:               Always
      CALICO_IPV4POOL_VXLAN:              Never
      CALICO_IPV6POOL_VXLAN:              Never
      FELIX_IPINIPMTU:                    <set to the key 'veth_mtu' of config map 'calico-config'>  Optional: false
      FELIX_VXLANMTU:                     <set to the key 'veth_mtu' of config map 'calico-config'>  Optional: false
      FELIX_WIREGUARDMTU:                 <set to the key 'veth_mtu' of config map 'calico-config'>  Optional: false
      CALICO_IPV4POOL_CIDR:               172.16.0.0/16
      CALICO_DISABLE_FILE_LOGGING:        true
      FELIX_DEFAULTENDPOINTTOHOSTACTION:  ACCEPT
      FELIX_IPV6SUPPORT:                  false
      FELIX_HEALTHENABLED:                true
    Mounts:
      /host/etc/cni/net.d from cni-net-dir (rw)
      /lib/modules from lib-modules (ro)
      /run/xtables.lock from xtables-lock (rw)
      /sys/fs/ from sysfs (rw)
      /var/lib/calico from var-lib-calico (rw)
      /var/log/calico/cni from cni-log-dir (ro)
      /var/run/calico from var-run-calico (rw)
      /var/run/nodeagent from policysync (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-54hkd (ro)
Conditions:
  Type              Status
  Initialized       False 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  lib-modules:
    Type:          HostPath (bare host directory volume)
    Path:          /lib/modules
    HostPathType:  
  var-run-calico:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/calico
    HostPathType:  
  var-lib-calico:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/calico
    HostPathType:  
  xtables-lock:
    Type:          HostPath (bare host directory volume)
    Path:          /run/xtables.lock
    HostPathType:  FileOrCreate
  sysfs:
    Type:          HostPath (bare host directory volume)
    Path:          /sys/fs/
    HostPathType:  DirectoryOrCreate
  cni-bin-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /opt/cni/bin
    HostPathType:  
  cni-net-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/cni/net.d
    HostPathType:  
  cni-log-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /var/log/calico/cni
    HostPathType:  
  host-local-net-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/cni/networks
    HostPathType:  
  policysync:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/nodeagent
    HostPathType:  DirectoryOrCreate
  kube-api-access-54hkd:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 :NoSchedule op=Exists
                             :NoExecute op=Exists
                             CriticalAddonsOnly op=Exists
                             node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason                  Age                   From               Message
  ----     ------                  ----                  ----               -------
  Normal   Scheduled               6m22s                 default-scheduler  Successfully assigned kube-system/calico-node-rwpfq to k8s3
  Warning  FailedCreatePodSandBox  62s (x26 over 6m21s)  kubelet            Failed to create pod sandbox: rpc error: code = NotFound desc = failed to get sandbox image "192.168.1.11:443/myharbor/pause:3.6": failed to pull image "192.168.1.11:443/myharbor/pause:3.6": failed to pull and unpack image "192.168.1.11:443/myharbor/pause:3.6": failed to resolve reference "192.168.1.11:443/myharbor/pause:3.6": 192.168.1.11:443/myharbor/pause:3.6: not found

  
 --找到原因:无法获取镜像。
  failed to get sandbox image "192.168.1.11:443/myharbor/pause:3.6"

3. 检查镜像 

[root@K8S1 soft]# docker images
REPOSITORY                                     TAG       IMAGE ID       CREATED       SIZE
192.168.1.11:443/myharbor/typha                v3.22.0   35c2fa1ee0a1   2 years ago   127MB
192.168.1.11:443/myharbor/kube-controllers     v3.22.0   df76d42861ee   2 years ago   132MB
192.168.1.11:443/myharbor/cni                  v3.22.0   f86797de8afd   2 years ago   236MB
192.168.1.11:443/myharbor/pod2daemon-flexvol   v3.22.0   59daef946c8c   2 years ago   21.4MB
192.168.1.11:443/myharbor/node                 v3.22.0   f109b1742d34   2 years ago   213MB

--果然没有pause镜像 ，导入镜像。
docker load < docker-pause_3.6.tar
...................
[root@K8S1 soft]# docker images
REPOSITORY                                     TAG       IMAGE ID       CREATED       SIZE
192.168.1.11:443/myharbor/typha                v3.22.0   35c2fa1ee0a1   2 years ago   127MB
192.168.1.11:443/myharbor/kube-controllers     v3.22.0   df76d42861ee   2 years ago   132MB
192.168.1.11:443/myharbor/cni                  v3.22.0   f86797de8afd   2 years ago   236MB
192.168.1.11:443/myharbor/pod2daemon-flexvol   v3.22.0   59daef946c8c   2 years ago   21.4MB
192.168.1.11:443/myharbor/node                 v3.22.0   f109b1742d34   2 years ago   213MB
192.168.1.11:443/myharbor/pause                3.6       6270bb605e12   2 years ago   683kB

4.重建calico网络

[root@K8S1 work]# kubectl delete -f /data/k8s/work/calico.yaml
configmap "calico-config" deleted
customresourcedefinition.apiextensions.k8s.io "bgpconfigurations.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "bgppeers.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "blockaffinities.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "caliconodestatuses.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "clusterinformations.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "felixconfigurations.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "globalnetworkpolicies.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "globalnetworksets.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "hostendpoints.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "ipamblocks.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "ipamconfigs.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "ipamhandles.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "ippools.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "ipreservations.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "kubecontrollersconfigurations.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "networkpolicies.crd.projectcalico.org" deleted
customresourcedefinition.apiextensions.k8s.io "networksets.crd.projectcalico.org" deleted
clusterrole.rbac.authorization.k8s.io "calico-kube-controllers" deleted
clusterrolebinding.rbac.authorization.k8s.io "calico-kube-controllers" deleted
clusterrole.rbac.authorization.k8s.io "calico-node" deleted
clusterrolebinding.rbac.authorization.k8s.io "calico-node" deleted
service "calico-typha" deleted
deployment.apps "calico-typha" deleted
poddisruptionbudget.policy "calico-typha" deleted
daemonset.apps "calico-node" deleted
serviceaccount "calico-node" deleted
deployment.apps "calico-kube-controllers" deleted
serviceaccount "calico-kube-controllers" deleted
poddisruptionbudget.policy "calico-kube-controllers" deleted

[root@K8S1 work]# kubectl apply -f /data/k8s/work/calico.yaml
configmap/calico-config created
customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/caliconodestatuses.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipreservations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/kubecontrollersconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org created
clusterrole.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrolebinding.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrole.rbac.authorization.k8s.io/calico-node created
clusterrolebinding.rbac.authorization.k8s.io/calico-node created
service/calico-typha created
deployment.apps/calico-typha created
poddisruptionbudget.policy/calico-typha created
daemonset.apps/calico-node created
serviceaccount/calico-node created
deployment.apps/calico-kube-controllers created
serviceaccount/calico-kube-controllers created
poddisruptionbudget.policy/calico-kube-controllers created

5.检查POD 

[root@K8S1 work]# kubectl get pod -A
NAMESPACE     NAME                                       READY   STATUS    RESTARTS   AGE
kube-system   calico-kube-controllers-554647c955-rb5fs   1/1     Running   0          33s
kube-system   calico-node-7zpwg                          1/1     Running   0          33s
kube-system   calico-node-9qrhz                          1/1     Running   0          33s
kube-system   calico-node-bvjnh                          1/1     Running   0          33s
kube-system   calico-node-vtnsr                          1/1     Running   0          33s
kube-system   calico-node-vvkdz                          1/1     Running   0          33s
kube-system   calico-node-zkxkq                          1/1     Running   0          33s
kube-system   calico-typha-6454f6cfd7-shs92              1/1     Running   0          33s

--果然calico 网络部署成功。

戒掉贪嗔痴(薛双奇)
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
laravel-model-status：轻松向模型添加状态
02-03
$ model -> setStatus ( 'pending' , 'needs verification' ); // set another status $ model -> setStatus ( 'accepted' ); // specify a reason $ model -> setStatus ( 'rejected' , 'My rejection reason' ); /...
wordpress获取文章状态函数：get_post_status()
01-20
‘pending’ – 文章正在等待审查 ‘draft’ – 草稿状态 ‘auto-draft’ – 自动保存的草稿 ‘future’ – 未来的时间发布 ‘private’ – 登录后可见 ‘inherit’ – 修订 ‘trash’ – 在回收站中.版本2.9.增加 ...
kubernetes pod一直是ContainerCreating,READY是0/1
愤怒的苹果ext的博客
06-27 5159
目录背景解决方案 背景 新创建的nginx-deployment，情况如下所示。 [root@localhost software]# kubectl get pods NAME READY STATUS RESTARTS AGE nginx-deployment-94093859-51185 0/1 ContainerCreating 0 11m nginx-deplo
coredns状态为pending和部署calico报错Init:0/3或Init:RunContainerError
崔崇鑫的博客，你linux/云运维工作中的百科全书。
12-06 8081
文章目录说明coredns报错状态和原因说明calico部署报错原因及处理报错部署说明报错Init:0/3说明及处理报错Init:RunContainerError部署正常显示内容，coredns状态正常了 说明 算是记录一个坑吧，tm的，折磨我好久了。各种查系统日至，百度，最后是找以前的环境对比出来的，日至报错奇奇怪怪，离谱的。 对了，如果k8s有问题，我们可以先看k8s日志，方式如下 先用kubectl get pods --all-namespaces -owide查看问题pod，然后用kub
K8s系列之：Pod的基本用法
zhengzaifeidelushang的博客
01-23 1448
K8s系列之：Pod的基本用法一、创建由一个容器组成名为frontend的Pod二、创建由frontend和redis两个容器组成一个名为redis-php的Pod三、静态Pod1）配置文件方式 Pod的基本用法为：Pod可以由1个或多个容器组合而成。 一、创建由一个容器组成名为frontend的Pod apiVersion: v1 kind: Pod metadata: name: frontend labels: - name: frontend spec: containers:
k8s报错：pod状态为pending，coredns的状态是pending的解决办法
热门推荐
baidu_38803985的博客
05-07 3万+
错误一：coredns的状态是pending 原因1：master上的flannel镜像拉取失败，导致获取不到解析的IP 解决方法： [root@master ~]# kubectl delete -f kube-flannel.yml #先删除安装的CNI插件 [root@master ~]# docker load --input flannel-0.11.0-amd64.tar #导...
Kubernetes排错(二)-pod状态异常原因分析
sre救赎之路
02-01 1819
pod异常状态排查方式
K8S篇之Pod一直处于Pending状态原因解析
xu710263124的博客
11-09 4145
Pod一直处于Pending原因解析
Kubernetes k8s pod 生命周期 init容器（初始化容器） 钩子配置
it知识分享 free for nothing..
07-02 687
Kubernetes k8s pod 生命周期 init容器（初始化容器） 钩子配置
彻底搞懂 K8S Pod Pending 故障原因及解决方案
xcbeyond|疯狂源自梦想，技术成就辉煌
05-04 2万+
点击上方“程序猿技术大咖”，关注并选择“设为星标”回复“加群”获取入群讨论资格！即使在高成熟度级别 Kubernetes 集群中 pod pending 也是无处不在。如果您随机询问任何使用 Kubernetes DevOps 工程师来确定折磨他们噩梦的最常见错误，pod pending 可能是非常常见的问题（可能仅次于 CrashLoopBackOff）。尝试推送更新并...
k8s 详解 pod 生命周期 容器探测(live and ready) 钩子函数 pod的重启策略
面朝大海，春暖花开
03-17 1854
pause 容器, 每个pod的都有的根容器,评估pod 的健康状态,设置ip地址,ip+端口可以访问到指定的容器 pod pod 之间采用 flannel 通信 pod 定义 yaml 资源清单 一级 二级 三级 属性 explain pod 一级属性 二级属性 点出来 三级属性,继续点 kubectl explain pod.metadata.managerFields status 状态,k8s 自动生成, spec 描述 ,当前资源的各种各样详...
k8s pod一直处于pending状态
qq_15138049的博客
11-03 1508
[root@hadoop03 k8s]# kubectl get pods NAME READY STATUS RESTARTS AGE nginx-controller-7c9j9 0/1 Pending 0 13m nginx-controller-pfnr7 0/1 Pending 0 13m [root@hadoop03 k8s]# kubectl describe pod
K8s常见问题分析&解决（未分类问题一）
01-07
1: Pod始终处于pending状态 详细描述： Pod始终处于pending状态 解题思路： 如果pod保持在pending的状态，意味着无法被正常的调度到节点上，由于系统的某些资源无法满足Pod的运行需求 原因分析： 系统没有足够...
k8s.gcr.io/coredns:1.2.2
11-01
使用方法请关注blog: https://blog.csdn.net/wenwst 导入命令： #docker load < coredns.1.2.2.tar # docker tag 367cdc8433a4 k8s.gcr.io/coredns:1.2.2
100-async-0-callback-conf::sparkles:https
05-11
Promise有三种状态：pending（进行中）、fulfilled（已完成）和rejected（已失败）。它通过链式调用来管理异步操作，使得代码更易读。 2. **async/await**：这是ES7引入的语法糖，基于Promise。async函数总是返回一...
K8S POD控制器：从基础到高级实战技巧
sdgfafg_25的博客
07-16 909
Kubernetes是由Google开发并捐赠给Cloud Native Computing Foundation的一个项目。它允许用户自动部署、扩展和管理容器化应用，并在提供这些服务的同时，保持高效和可靠。Kubernetes的核心组件之一是POD，它是Kubernetes应用程序的基本执行单元。一个POD中可以包含一个或多个容器，这些容器共享存储、网络和运行配置。在Kubernetes中，POD控制器则是负责确保POD的生命周期管理。它们确保在任何给定时间，集群中都有正确数量的POD副本在运行。
[k8s源码]4.informer
weixin_45396500的博客
07-16 711
这段代码定义了 PodInformer 接口及其实现，采用了工厂模式和延迟初始化策略来管理 Kubernetes Pod 资源的 Informer。核心是 Informer() 方法，它通过调用 factory.InformerFor() 来获取或创建 cache.SharedIndexInformer 实例。这个过程的本质是构造一个 cache.SharedIndexInformer 类型的 informer。
使用Velero备份与恢复K8s集群及应用
最新发布
07-19 645
备份容灾一键恢复集群迁移支持备份pv，备份数据加密，通过两种备份插件实现，通过启动命令upload-type参数更改。
RKE部署k8s
professorman的博客
07-19 165
安装成功之后会在当前目录生成kube_config_cluster.yml文件，此为k8s的kube_config文件，需要配置kubectl默认读取文件才可执行kubectl命令进行查询。如果需要增加node节点或者etcd节点，只需要更改cluster.yml后rke up --update-only即可。则在install的时候加上。此处密码最少12个字符。rke部署k8s集群。
k8s pod pending状态的原因
06-09
Kubernetes中Pod处于Pending状态的原因可能有以下几种： 1. 没有足够的资源：Kubernetes调度器无法为Pod分配足够的资源，例如CPU、内存或磁盘空间。 2. 调度器无法找到合适的节点：如果没有节点有足够的资源来满足Pod的要求，Pod将一直处于Pending状态，直到有足够的资源可用为止。 3. Pod的调度限制：如果Pod的调度限制与节点的标签不匹配，Pod将无法与节点匹配，并且将一直处于Pending状态。 4. 网络问题：如果Pod所需的网络服务不存在或无法访问，Pod将无法启动，并将一直处于Pending状态。 5. 存储问题：如果Pod需要的存储卷无法挂载或访问，Pod将无法启动并将一直处于Pending状态。 要解决这些问题，可以通过查看Pod的事件日志来确定具体的原因，并尝试解决它们。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值