[root@k8s-master01 ~]# kubectl get pod
NAME READY STATUS RESTARTS AGE
nginx-deployment-975645775-mjspl 0/1 CrashLoopBackOff 7 13m
nginx-deployment1-574c4f95df-t8v6t 1/1 Running 0 92m
- 其中的nginx-deployment,状态一直异常,显示为CrashLoopBackOff,使用kubectl delete pod
nginx-deployment-975645775-mjspl --grace-period=0
–force强制删除后,由于运行此pod时,“kubectl run nginx-deployment --image=hub.atguigu.com/library/myapp:v1 --port=80 --replicas=1”,设置了副本数为1,所以当删除这个pod时,k8s系统为了保持此pod副本为1会创建一个新的副本pod,导致删除成功后,kubectl
get pod 仍然显示有一个pod。 此时,将这个pod的副本期望设置为0 ,再次执行删除命令,就可以成功删除。
kubectl scale --replicas=0 deployment/nginx-deployment
可以看到前后对比,第一个状态异常的nginx-deployment已经被成功删除
[root@k8s-master01 ~]# kubectl get pod
NAME READY STATUS RESTARTS AGE
nginx-deployment-975645775-mjspl 0/1 CrashLoopBackOff 7 13m
nginx-deployment1-574c4f95df-t8v6t 1/1 Running 0 92m
[root@k8s-master01 ~]# kubectl scale --replicas=0 deployment/nginx-deployment
deployment.extensions/nginx-deployment scaled
[root@k8s-master01 ~]# kubectl get pod
NAME READY STATUS RESTARTS AGE
nginx-deployment1-574c4f95df-t8v6t 1/1 Running 0 93m