千家信息网

K8S Pod status的状态分析

发表于:2025-12-02 作者:千家信息网编辑
千家信息网最后更新 2025年12月02日,K8S Pod status的状态分析CrashLoopBackOff: 容器退出,kubelet正在将它重启InvalidImageName: 无法解析镜像名称ImageInspectError:
千家信息网最后更新 2025年12月02日K8S Pod status的状态分析

K8S Pod status的状态分析

CrashLoopBackOff: 容器退出,kubelet正在将它重启InvalidImageName: 无法解析镜像名称ImageInspectError: 无法校验镜像ErrImageNeverPull: 策略禁止拉取镜像ImagePullBackOff: 正在重试拉取RegistryUnavailable: 连接不到镜像中心ErrImagePull: 通用的拉取镜像出错CreateContainerConfigError: 不能创建kubelet使用的容器配置CreateContainerError: 创建容器失败m.internalLifecycle.PreStartContainer  执行hook报错RunContainerError: 启动容器失败PostStartHookError: 执行hook报错 ContainersNotInitialized: 容器没有初始化完毕ContainersNotReady: 容器没有准备完毕 ContainerCreating:容器创建中PodInitializing:pod 初始化中 DockerDaemonNotReady:docker还没有完全启动NetworkPluginNotReady: 网络插件还没有完全启动

K8S-YAML的使用及命令

YAML配置文件管理对象对象管理:# 创建deployment资源kubectl create -f nginx-deployment.yaml# 查看deploymentkubectl get deploy# 查看ReplicaSetkubectl get rs# 查看pods所有标签kubectl get pods --show-labels# 根据标签查看podskubectl get pods -l app=nginx# 滚动更新镜像kubectl set image deployment/nginx-deployment nginx=nginx:1.11或者kubectl edit deployment/nginx-deployment或者kubectl apply -f nginx-deployment.yaml# 实时观察发布状态:kubectl rollout status deployment/nginx-deployment# 查看deployment历史修订版本kubectl rollout history deployment/nginx-deploymentkubectl rollout history deployment/nginx-deployment --revision=3# 回滚到以前版本kubectl rollout undo deployment/nginx-deploymentkubectl rollout undo deployment/nginx-deployment --to-revision=3# 扩容deployment的Pod副本数量kubectl scale deployment nginx-deployment --replicas=10# 设置启动扩容/缩容kubectl autoscale deployment nginx-deployment --min=10 --max=15 --cpu-percent=80

对象管理实例:vim nginx.deployment.yaml

apiVersion: apps/v1beta2kind: Deploymentmetadata:  name: nginx-deploymentspec:  replicas: 2  selector:    matchLabels:      app: nginx  template:    metadata:      labels:        app: nginx    spec:      containers:      - name: nginx        image: nginx:1.10        ports:        - containerPort: 80

服务发现实例:vim nging.service.yaml

apiVersion: v1kind: Servicemetadata:  labels:    run: nginx  name: nginx  namespace: defaultspec:  ports:  - port: 88    targetPort: 80  selector:    app: nginx

清理:

# kubectl delete -f nginx-deployment.yaml

# kubectl delete -f nginx-service.yaml

POD作用:

Pod管理-创建/查询/更新/删除基本管理:# 创建pod资源kubectl create -f pod.yaml# 查看podskubectl get pods pod-test# 查看pod描述kubectl describe pod pod-test# 替换资源kubectl replace -f pod.yaml -force# 删除资源kubectl delete pod pod-test

支持三种策略:

Always:当容器终止退出后,总是重启容器,默认策略。

OnFailure:当容器异常退出(退出状态码非0)时,才重启容器。

Never:当容器终止退出,从不重启容器。

Pod实例:vim pod.yaml

apiVersion: v1kind: Podmetadata:  name: pod-test  labels:     os: centosspec:  containers:  - name: hello    image: centos:7    env:    - name: Test      value: "123456"    command: ["bash","-c","while true;do date;sleep 1;done"]  restartPolicy: OnFailure

Pod管理-健康检查:

提供Probe机制,有以下两种类型:livenessProbe如果检查失败,将杀死容器,然后根据Pod的重启策略来决定是否重启。readinessProbe如果检查失败,Kubernetes会把Pod从服务代理的分发后端剔除。Probe支持以下三种检查方法:httpGet发送HTTP请求,返回200-400范围状态码为成功。exec执行Shell命令返回状态码是0为成功。tcpSocket发起TCP Socket建立成功。

实例:vim pod2.yaml

apiVersion: v1kind: Podmetadata:  name: nginx-pod  labels:    app: nginxspec:  containers:  - name: nginx    image: nginx:1.10    ports:    - containerPort: 80    livenessProbe:      httpGet:        path: /index.html        port: 80

Pod管理-数据持久化和共享:

vim pod3.yaml

apiVersion: v1kind: Podmetadata:  name: pod-test1  labels:     test: centosspec:  containers:  # 第一个容器  - name: hello-write    image: centos:7    command: ["bash","-c","for i in {1..1000};do echo $i >> /data/hello;sleep 1;done"]  # 第二个容器  - name: hello-read    image: centos:7    command: ["bash","-c","for i in {1..1000};do cat $i >> /data/hello;sleep 1;done"]    volumeMounts:      - name: data        mountPath: /data  # 数据卷  volumes:  - name: data    hostPath:      path: /data

Pod端口映射:

vim pod4.yaml

apiVersion: v1kind: Podmetadata:  name: nginx-pod  labels:    app: nginxspec:  containers:  - name: nginx    image: nginx:1.10    ports:    - name: http      containerPort: 80      hostIP: 0.0.0.0      hostPort: 80      protocol: TCP   - name: https     containerPort: 443     hostIP: 0.0.0.0     hostPort: 443     protocol: TCP
0