可以看到node3上有 5个pod

[root@VM-2-5-centos ~]# kubectl get pod -A -owide
NAMESPACE     NAME                                      READY   STATUS    RESTARTS   AGE     IP               NODE             NOMINATED NODE   READINESS GATES
kube-system   calico-kube-controllers-97769f7c7-8hk6l   1/1     Running   0          4h25m   10.244.169.193   vm-2-15-centos   <none>           <none>
kube-system   calico-node-gxlpl                         1/1     Running   0          4h25m   172.16.2.3       vm-2-3-centos    <none>           <none>
kube-system   calico-node-mlbg4                         1/1     Running   0          4h25m   172.16.2.15      vm-2-15-centos   <none>           <none>
kube-system   calico-node-sxdfw                         1/1     Running   0          4h25m   172.16.2.5       vm-2-5-centos    <none>           <none>
kube-system   coredns-7f89b7bc75-lgvr2                  1/1     Running   0          4h28m   10.244.169.194   vm-2-15-centos   <none>           <none>
kube-system   coredns-7f89b7bc75-phvhn                  1/1     Running   0          4h28m   10.244.169.195   vm-2-15-centos   <none>           <none>
kube-system   etcd-vm-2-5-centos                        1/1     Running   0          4h28m   172.16.2.5       vm-2-5-centos    <none>           <none>
kube-system   kube-apiserver-vm-2-5-centos              1/1     Running   0          4h28m   172.16.2.5       vm-2-5-centos    <none>           <none>
kube-system   kube-controller-manager-vm-2-5-centos     1/1     Running   0          4h28m   172.16.2.5       vm-2-5-centos    <none>           <none>
kube-system   kube-proxy-8pcct                          1/1     Running   0          4h27m   172.16.2.15      vm-2-15-centos   <none>           <none>
kube-system   kube-proxy-br94b                          1/1     Running   0          4h27m   172.16.2.3       vm-2-3-centos    <none>           <none>
kube-system   kube-proxy-z2xcz                          1/1     Running   0          4h28m   172.16.2.5       vm-2-5-centos    <none>           <none>
kube-system   kube-scheduler-vm-2-5-centos              1/1     Running   0          4h28m   172.16.2.5       vm-2-5-centos    <none>           <none>
kube-system   metrics-server-b66888848-kdf7q            1/1     Running   0          4h23m   10.244.71.1      vm-2-3-centos    <none>           <none>
[root@VM-2-5-centos ~]# kubectl get node
NAME             STATUS   ROLES                  AGE     VERSION
vm-2-15-centos   Ready    <none>                 4h27m   v1.20.4
vm-2-3-centos    Ready    <none>                 4h28m   v1.20.4
vm-2-5-centos    Ready    control-plane,master   4h29m   v1.20.4

设置pod 不可调度 

[root@VM-2-5-centos ~]# kubectl cordon vm-2-15-centos
node/vm-2-15-centos cordoned
[root@VM-2-5-centos ~]# kubectl get node
NAME             STATUS                     ROLES                  AGE     VERSION
vm-2-15-centos   Ready,SchedulingDisabled   <none>                 4h28m   v1.20.4
vm-2-3-centos    Ready                      <none>                 4h28m   v1.20.4
vm-2-5-centos    Ready                      control-plane,master   4h30m   v1.20.4

 驱逐node3 上的 pod,报错

[root@VM-2-5-centos ~]# kubectl drain vm-2-15-centos --ignore-daemonsets=false
node/vm-2-15-centos already cordoned
error: unable to drain node "vm-2-15-centos", aborting command...

There are pending nodes to be drained:
 vm-2-15-centos
error: cannot delete DaemonSet-managed Pods (use --ignore-daemonsets to ignore): kube-system/calico-node-mlbg4, kube-system/kube-proxy-8pcct

 再次执行,告警:daemonset 无法驱逐,不用管,一般接收流量的pod 被驱逐就好了

[root@VM-2-5-centos ~]# kubectl drain vm-2-15-centos --ignore-daemonsets 
node/vm-2-15-centos already cordoned
WARNING: ignoring DaemonSet-managed Pods: kube-system/calico-node-mlbg4, kube-system/kube-proxy-8pcct
evicting pod kube-system/coredns-7f89b7bc75-phvhn
evicting pod kube-system/calico-kube-controllers-97769f7c7-8hk6l
evicting pod kube-system/coredns-7f89b7bc75-lgvr2
pod/calico-kube-controllers-97769f7c7-8hk6l evicted
pod/coredns-7f89b7bc75-phvhn evicted
pod/coredns-7f89b7bc75-lgvr2 evicted
node/vm-2-15-centos evicted

 可以看到node是不可用状态

[root@VM-2-5-centos ~]# kubectl get node -A
NAME             STATUS                     ROLES                  AGE     VERSION
vm-2-15-centos   Ready,SchedulingDisabled   <none>                 4h32m   v1.20.4
vm-2-3-centos    Ready                      <none>                 4h32m   v1.20.4
vm-2-5-centos    Ready                      control-plane,master   4h33m   v1.20.4

删除node

[root@VM-2-5-centos ~]# kubectl delete node  vm-2-15-centos
node "vm-2-15-centos" deleted

 这里我们可以看到node被删除,pod 还没消失,还有2个daemonset 程序这里需要等待30s

[root@VM-2-5-centos ~]# kubectl get pod  -A -owide
NAMESPACE     NAME                                      READY   STATUS    RESTARTS   AGE     IP            NODE             NOMINATED NODE   READINESS GATES
kube-system   calico-kube-controllers-97769f7c7-zjpr6   1/1     Running   0          102s    10.244.71.2   vm-2-3-centos    <none>           <none>
kube-system   calico-node-gxlpl                         1/1     Running   0          4h32m   172.16.2.3    vm-2-3-centos    <none>           <none>
kube-system   calico-node-mlbg4                         1/1     Running   0          4h32m   172.16.2.15   vm-2-15-centos   <none>           <none>
kube-system   calico-node-sxdfw                         1/1     Running   0          4h32m   172.16.2.5    vm-2-5-centos    <none>           <none>
kube-system   coredns-7f89b7bc75-5d29s                  1/1     Running   0          102s    10.244.71.3   vm-2-3-centos    <none>           <none>
kube-system   coredns-7f89b7bc75-6rl9q                  1/1     Running   0          102s    10.244.71.4   vm-2-3-centos    <none>           <none>
kube-system   etcd-vm-2-5-centos                        1/1     Running   0          4h34m   172.16.2.5    vm-2-5-centos    <none>           <none>
kube-system   kube-apiserver-vm-2-5-centos              1/1     Running   0          4h34m   172.16.2.5    vm-2-5-centos    <none>           <none>
kube-system   kube-controller-manager-vm-2-5-centos     1/1     Running   0          4h34m   172.16.2.5    vm-2-5-centos    <none>           <none>
kube-system   kube-proxy-8pcct                          1/1     Running   0          4h33m   172.16.2.15   vm-2-15-centos   <none>           <none>
kube-system   kube-proxy-br94b                          1/1     Running   0          4h33m   172.16.2.3    vm-2-3-centos    <none>           <none>
kube-system   kube-proxy-z2xcz                          1/1     Running   0          4h34m   172.16.2.5    vm-2-5-centos    <none>           <none>
kube-system   kube-scheduler-vm-2-5-centos              1/1     Running   0          4h34m   172.16.2.5    vm-2-5-centos    <none>           <none>
kube-system   metrics-server-b66888848-kdf7q            1/1     Running   0          4h29m   10.244.71.1   vm-2-3-centos    <none>           <none>
[root@VM-2-5-centos ~]# kubectl get node 
NAME            STATUS   ROLES                  AGE     VERSION
vm-2-3-centos   Ready    <none>                 4h34m   v1.20.4
vm-2-5-centos   Ready    control-plane,master   4h35m   v1.20.4

 再次查看已删除

[root@VM-2-5-centos ~]# kubectl get pod  -A -owide
NAMESPACE     NAME                                      READY   STATUS    RESTARTS   AGE     IP            NODE            NOMINATED NODE   READINESS GATES
kube-system   calico-kube-controllers-97769f7c7-zjpr6   1/1     Running   0          2m50s   10.244.71.2   vm-2-3-centos   <none>           <none>
kube-system   calico-node-gxlpl                         1/1     Running   0          4h33m   172.16.2.3    vm-2-3-centos   <none>           <none>
kube-system   calico-node-sxdfw                         1/1     Running   0          4h33m   172.16.2.5    vm-2-5-centos   <none>           <none>
kube-system   coredns-7f89b7bc75-5d29s                  1/1     Running   0          2m50s   10.244.71.3   vm-2-3-centos   <none>           <none>
kube-system   coredns-7f89b7bc75-6rl9q                  1/1     Running   0          2m50s   10.244.71.4   vm-2-3-centos   <none>           <none>
kube-system   etcd-vm-2-5-centos                        1/1     Running   0          4h36m   172.16.2.5    vm-2-5-centos   <none>           <none>
kube-system   kube-apiserver-vm-2-5-centos              1/1     Running   0          4h36m   172.16.2.5    vm-2-5-centos   <none>           <none>
kube-system   kube-controller-manager-vm-2-5-centos     1/1     Running   0          4h36m   172.16.2.5    vm-2-5-centos   <none>           <none>
kube-system   kube-proxy-br94b                          1/1     Running   0          4h35m   172.16.2.3    vm-2-3-centos   <none>           <none>
kube-system   kube-proxy-z2xcz                          1/1     Running   0          4h35m   172.16.2.5    vm-2-5-centos   <none>           <none>
kube-system   kube-scheduler-vm-2-5-centos              1/1     Running   0          4h36m   172.16.2.5    vm-2-5-centos   <none>           <none>
kube-system   metrics-server-b66888848-kdf7q            1/1     Running   0          4h30m   10.244.71.1   vm-2-3-centos   <none>           <none>

Logo

K8S/Kubernetes社区为您提供最前沿的新闻资讯和知识内容

更多推荐