kubectl apply -f 的逆向操作是什么
来源：6-6 部署ingress-nginx（下）
zjg23
2019-12-24
刚开始用的最新的mandatory.yaml文件，后来切换成课程git上的mandatory.yaml文件。
请问怎么把之前这条命令：
kubectl apply -f mandatory.yaml
的执行结果回滚掉？
注：删除原来的deployment、pod，执行kubectl apply -f mandatory.yaml后，
跟视频中比较少一个pod，且ready和available都有0.
[root@m3 ingress-nginx]# kubectl get all -n ingress-nginx
NAME READY STATUS RESTARTS AGE
pod/nginx-ingress-controller-84c5d78fd5-ncz78 1/1 Running 0 6m9s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/default-http-backend ClusterIP 10.100.57.213 80/TCP 6m9s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/default-http-backend 0/1 0 0 6m10s
deployment.apps/nginx-ingress-controller 1/1 1 1 6m9s
NAME DESIRED CURRENT READY AGE
replicaset.apps/default-http-backend-5c9bb94849 1 0 0 6m10s
replicaset.apps/nginx-ingress-controller-84c5d78fd5 1 1 1 6m9s
1回答
-
zjg23
提问者
2019-12-24
自问自答一下：
kubectl delete -f mandatory.yaml
删除后重新apply，状态正常：
[root@m3 ingress-nginx]# kubectl get all -n ingress-nginx
NAME READY STATUS RESTARTS AGE
pod/default-http-backend-5c9bb94849-f62vw 1/1 Running 0 64s
pod/nginx-ingress-controller-84c5d78fd5-qrktm 1/1 Running 0 63s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/default-http-backend ClusterIP 10.100.159.23 <none> 80/TCP 64s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/default-http-backend 1/1 1 1 64s
deployment.apps/nginx-ingress-controller 1/1 1 1 63s
NAME DESIRED CURRENT READY AGE
replicaset.apps/default-http-backend-5c9bb94849 1 1 1 64s
replicaset.apps/nginx-ingress-controller-84c5d78fd5 1 1 1 63s
10
相似问题