k8s 구성요소

# kube-system에 배포된 Pod 확인 [root@m-k8s ~]# kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE calico-kube-controllers-6856fc6d6c-zhmmp 1/1 Running 0 25h calico-node-bghzp 1/1 Running 0 25h calico-node-n7hnn 1/1 Running 0 25h calico-node-qntqg 1/1 Running 0 25h calico-node-tb9w4 1/1 Running 0 25h coredns-565d847f94-ff2px 1/1 Running 0 25h coredns-565d847f94-qgwwx 1/1 Running 0 25h etcd-m-k8s 1/1 Running 0 25h kube-apiserver-m-k8s 1/1 Running 0 25h kube-controller-manager-m-k8s 1/1 Running 0 25h kube-proxy-cph5z 1/1 Running 0 25h kube-proxy-crj82 1/1 Running 0 25h kube-proxy-dtwj7 1/1 Running 0 25h kube-proxy-wkkxt 1/1 Running 0 25h kube-scheduler-m-k8s 1/1 Running 0 25h

# w1-k8s 워커노드에서 kubelet 중지 [root@w1-k8s ~]# systemctl stop kubelet # 마스터노드에서 배포 [root@m-k8s ~]# kubectl apply -f ~/_Lecture_k8s_starter.kit/ch4/4.1/del-deploy.yaml deployment.apps/del-deploy created # Pod를 확인해보면 STATUS가 Pending으로 배포가 이루어지지 않음 [root@m-k8s ~]# kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES del-deploy-7b68dfdb46-dj8b8 0/1 Pending 0 8s <none> w1-k8s <none> <none> del-deploy-7b68dfdb46-l7zvt 1/1 Running 0 8s 172.16.132.4 w3-k8s <none> <none> del-deploy-7b68dfdb46-pn99s 1/1 Running 0 8s 172.16.103.132 w2-k8s <none> <none> # w1-k8s 워커노드에서 kubelet 시작 [root@w1-k8s ~]# systemctl start kubelet # Pod를 확인해보면 STATUS가 Running으로 배포가 이루어짐 [root@m-k8s ~]# kubectl get pods -o wide -w NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES del-deploy-7b68dfdb46-dj8b8 1/1 Running 0 2m19s 172.16.221.132 w1-k8s <none> <none> del-deploy-7b68dfdb46-l7zvt 1/1 Running 0 2m19s 172.16.132.4 w3-k8s <none> <none> del-deploy-7b68dfdb46-pn99s 1/1 Running 0 2m19s 172.16.103.132 w2-k8s <none> <none>

# 현재 Pod 배포 상태 확인 [root@m-k8s ~]# kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES del-deploy-7b68dfdb46-dj8b8 1/1 Running 0 6m9s 172.16.221.132 w1-k8s <none> <none> del-deploy-7b68dfdb46-l7zvt 1/1 Running 0 6m9s 172.16.132.4 w3-k8s <none> <none> del-deploy-7b68dfdb46-pn99s 1/1 Running 0 6m9s 172.16.103.132 w2-k8s <none> <none> # 워커노드에서 containerd 중지 [root@w1-k8s ~]# systemctl stop containerd # Pod를 6으로 스케일 [root@m-k8s ~]# kubectl scale deployment del-deploy --replicas=6 deployment.apps/del-deploy scaled # Pod가 w1-k8s워커노드로는 배포되지 않음 [root@m-k8s ~]# kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES del-deploy-7b68dfdb46-dgg5x 1/1 Running 0 6s 172.16.103.133 w2-k8s <none> <none> del-deploy-7b68dfdb46-dj8b8 1/1 Running 0 7m19s 172.16.221.132 w1-k8s <none> <none> del-deploy-7b68dfdb46-kh58q 0/1 ContainerCreating 0 6s <none> w3-k8s <none> <none> del-deploy-7b68dfdb46-l7zvt 1/1 Running 0 7m19s 172.16.132.4 w3-k8s <none> <none> del-deploy-7b68dfdb46-pn99s 1/1 Running 0 7m19s 172.16.103.132 w2-k8s <none> <none> del-deploy-7b68dfdb46-r9ln6 1/1 Running 0 6s 172.16.132.5 w3-k8s <none> <none> # 5분이 지나면 w1-k8s 워커노드가 Terminating 상태가 됨 [root@m-k8s ~]# kubectl get pods -o wide -w NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES del-deploy-7b68dfdb46-dgg5x 1/1 Running 0 9m1s 172.16.103.133 w2-k8s <none> <none> del-deploy-7b68dfdb46-dj8b8 1/1 Terminating 0 16m 172.16.221.132 w1-k8s <none> <none> del-deploy-7b68dfdb46-kh58q 1/1 Running 0 9m1s 172.16.132.6 w3-k8s <none> <none> del-deploy-7b68dfdb46-l7zvt 1/1 Running 0 16m 172.16.132.4 w3-k8s <none> <none> del-deploy-7b68dfdb46-pn99s 1/1 Running 0 16m 172.16.103.132 w2-k8s <none> <none> del-deploy-7b68dfdb46-r9ln6 1/1 Running 0 9m1s 172.16.132.5 w3-k8s <none> <none> del-deploy-7b68dfdb46-xpkxb 1/1 Running 0 4m6s 172.16.103.134 w2-k8s <none> <none>

# 워커노드에서 containerd 시작 [root@w1-k8s ~]# systemctl start containerd # Pod를 9으로 스케일 [root@m-k8s ~]# kubectl scale deployment del-deploy --replicas=9 deployment.apps/del-deploy scaled # ContainerD가 올라온것을 스케줄러가 파악하지 못해서 균등하게 배포를 하지 못 함 [root@m-k8s ~]# kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES del-deploy-7b68dfdb46-9ctgx 1/1 Running 0 7s 172.16.132.7 w3-k8s <none> <none> del-deploy-7b68dfdb46-dgg5x 1/1 Running 0 11m 172.16.103.133 w2-k8s <none> <none> del-deploy-7b68dfdb46-dj8b8 1/1 Terminating 0 18m 172.16.221.132 w1-k8s <none> <none> del-deploy-7b68dfdb46-jzd6l 1/1 Running 0 7s 172.16.132.8 w3-k8s <none> <none> del-deploy-7b68dfdb46-kh58q 1/1 Running 0 11m 172.16.132.6 w3-k8s <none> <none> del-deploy-7b68dfdb46-l7zvt 1/1 Running 0 18m 172.16.132.4 w3-k8s <none> <none> del-deploy-7b68dfdb46-md2j2 1/1 Running 0 7s 172.16.103.136 w2-k8s <none> <none> del-deploy-7b68dfdb46-pn99s 1/1 Running 0 18m 172.16.103.132 w2-k8s <none> <none> del-deploy-7b68dfdb46-r9ln6 1/1 Running 0 11m 172.16.132.5 w3-k8s <none> <none> del-deploy-7b68dfdb46-xpkxb 1/1 Running 0 6m37s 172.16.103.134 w2-k8s <none> <none> # Pod를 0으로 Terminating 시켰다가 다시 9로 스케일 [root@m-k8s ~]# kubectl scale deployment del-deploy --replicas=0 deployment.apps/del-deploy scaled [root@m-k8s ~]# kubectl get pod -o wide No resources found in default namespace. [root@m-k8s ~]# kubectl scale deployment del-deploy --replicas=9 deployment.apps/del-deploy scaled # ContainerD가 올라온것을 스케줄러가 파악하여 균등하게 배포함 [root@m-k8s ~]# kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES del-deploy-7b68dfdb46-24zv4 0/1 ContainerCreating 0 3s <none> w3-k8s <none> <none> del-deploy-7b68dfdb46-6hhmx 0/1 ContainerCreating 0 3s <none> w1-k8s <none> <none> del-deploy-7b68dfdb46-7jdlz 0/1 ContainerCreating 0 3s <none> w2-k8s <none> <none> del-deploy-7b68dfdb46-9h6ph 0/1 ContainerCreating 0 3s <none> w3-k8s <none> <none> del-deploy-7b68dfdb46-9ztks 0/1 ContainerCreating 0 3s <none> w3-k8s <none> <none> del-deploy-7b68dfdb46-m2f5d 0/1 ContainerCreating 0 3s <none> w2-k8s <none> <none> del-deploy-7b68dfdb46-pxvrm 0/1 ContainerCreating 0 3s <none> w2-k8s <none> <none> del-deploy-7b68dfdb46-tn42d 0/1 ContainerCreating 0 3s <none> w1-k8s <none> <none> del-deploy-7b68dfdb46-w87b5 0/1 ContainerCreating 0 3s <none> w1-k8s <none> <none>

# kube-system 네임스페이스 내 pods 확인 [root@m-k8s ~]# kubectl get pods -n kube-system -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES calico-kube-controllers-6856fc6d6c-w7zd5 1/1 Running 0 14m 172.16.103.135 w2-k8s <none> <none> calico-node-bghzp 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> calico-node-n7hnn 1/1 Running 0 2d 192.168.1.103 w3-k8s <none> <none> calico-node-qntqg 1/1 Running 0 2d 192.168.1.102 w2-k8s <none> <none> calico-node-tb9w4 1/1 Running 0 2d 192.168.1.101 w1-k8s <none> <none> coredns-565d847f94-ff2px 1/1 Running 0 2d 172.16.171.65 m-k8s <none> <none> coredns-565d847f94-qgwwx 1/1 Running 0 2d 172.16.171.66 m-k8s <none> <none> etcd-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-apiserver-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-controller-manager-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-proxy-cph5z 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-proxy-crj82 1/1 Running 0 2d 192.168.1.101 w1-k8s <none> <none> kube-proxy-dtwj7 1/1 Running 0 2d 192.168.1.102 w2-k8s <none> <none> kube-proxy-wkkxt 1/1 Running 0 2d 192.168.1.103 w3-k8s <none> <none> kube-scheduler-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> # 스케줄러 삭제 [root@m-k8s ~]# kubectl delete pod kube-scheduler-m-k8s -n kube-system pod "kube-scheduler-m-k8s" deleted # 스케줄러가 다시 생성된것이 확인됨 [root@m-k8s ~]# kubectl get pods -n kube-system -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES calico-kube-controllers-6856fc6d6c-w7zd5 1/1 Running 0 16m 172.16.103.135 w2-k8s <none> <none> calico-node-bghzp 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> calico-node-n7hnn 1/1 Running 0 2d 192.168.1.103 w3-k8s <none> <none> calico-node-qntqg 1/1 Running 0 2d 192.168.1.102 w2-k8s <none> <none> calico-node-tb9w4 1/1 Running 0 2d 192.168.1.101 w1-k8s <none> <none> coredns-565d847f94-ff2px 1/1 Running 0 2d 172.16.171.65 m-k8s <none> <none> coredns-565d847f94-qgwwx 1/1 Running 0 2d 172.16.171.66 m-k8s <none> <none> etcd-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-apiserver-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-controller-manager-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-proxy-cph5z 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-proxy-crj82 1/1 Running 0 2d 192.168.1.101 w1-k8s <none> <none> kube-proxy-dtwj7 1/1 Running 0 2d 192.168.1.102 w2-k8s <none> <none> kube-proxy-wkkxt 1/1 Running 0 2d 192.168.1.103 w3-k8s <none> <none> kube-scheduler-m-k8s 1/1 Running 0 18s 192.168.1.10 m-k8s <none> <none>

# kubelet 중지 [root@m-k8s ~]# systemctl stop kubelet # 스케줄러 삭제 시 프롬프트가 떨어지지 않고 멈춰있음 [root@m-k8s ~]# kubectl delete pod kube-scheduler-m-k8s -n kube-system pod "kube-scheduler-m-k8s" deleted ^c # 명령이 kubelet을 통해서 전달되지 않기 때문에 Terminating이라고 뜨지만 실제로 삭제되지 않음 [root@m-k8s ~]kubectl get pods -n kube-system -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES calico-kube-controllers-6856fc6d6c-w7zd5 1/1 Running 0 26m 172.16.103.135 w2-k8s <none> <none> calico-node-bghzp 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> calico-node-n7hnn 1/1 Running 0 2d 192.168.1.103 w3-k8s <none> <none> calico-node-qntqg 1/1 Running 0 2d 192.168.1.102 w2-k8s <none> <none> calico-node-tb9w4 1/1 Running 0 2d 192.168.1.101 w1-k8s <none> <none> coredns-565d847f94-ff2px 1/1 Running 0 2d 172.16.171.65 m-k8s <none> <none> coredns-565d847f94-qgwwx 1/1 Running 0 2d 172.16.171.66 m-k8s <none> <none> etcd-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-apiserver-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-controller-manager-m-k8s 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-proxy-cph5z 1/1 Running 0 2d 192.168.1.10 m-k8s <none> <none> kube-proxy-crj82 1/1 Running 0 2d 192.168.1.101 w1-k8s <none> <none> kube-proxy-dtwj7 1/1 Running 0 2d 192.168.1.102 w2-k8s <none> <none> kube-proxy-wkkxt 1/1 Running 0 2d 192.168.1.103 w3-k8s <none> <none> kube-scheduler-m-k8s 1/1 Terminating 0 10m 192.168.1.10 m-k8s <none> <none> # nginx pod 배포 [root@m-k8s ~]# kubectl create deployment nginx --image=nginx deployment.apps/nginx created # 배포가 정상적으로 된 것이 확인됨 [root@m-k8s ~]# kubectl get pod NAME READY STATUS RESTARTS AGE del-deploy-7b68dfdb46-24zv4 1/1 Running 0 20m del-deploy-7b68dfdb46-6hhmx 1/1 Running 0 20m del-deploy-7b68dfdb46-7jdlz 1/1 Running 0 20m del-deploy-7b68dfdb46-9h6ph 1/1 Running 0 20m del-deploy-7b68dfdb46-9ztks 1/1 Running 0 20m del-deploy-7b68dfdb46-m2f5d 1/1 Running 0 20m del-deploy-7b68dfdb46-pxvrm 1/1 Running 0 20m del-deploy-7b68dfdb46-tn42d 1/1 Running 0 20m del-deploy-7b68dfdb46-w87b5 1/1 Running 0 20m nginx-76d6c9b8c-lnlwz 1/1 Running 0 4s # 3으로 스케일 [root@m-k8s ~]# kubectl scale deployment nginx --replicas=3 deployment.apps/nginx scaled # 스케일이 정상적으로 된 것이 확인됨 [root@m-k8s ~]# kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES del-deploy-7b68dfdb46-24zv4 1/1 Running 0 22m 172.16.132.9 w3-k8s <none> <none> del-deploy-7b68dfdb46-6hhmx 1/1 Running 0 22m 172.16.221.133 w1-k8s <none> <none> del-deploy-7b68dfdb46-7jdlz 1/1 Running 0 22m 172.16.103.138 w2-k8s <none> <none> del-deploy-7b68dfdb46-9h6ph 1/1 Running 0 22m 172.16.132.11 w3-k8s <none> <none> del-deploy-7b68dfdb46-9ztks 1/1 Running 0 22m 172.16.132.10 w3-k8s <none> <none> del-deploy-7b68dfdb46-m2f5d 1/1 Running 0 22m 172.16.103.137 w2-k8s <none> <none> del-deploy-7b68dfdb46-pxvrm 1/1 Running 0 22m 172.16.103.139 w2-k8s <none> <none> del-deploy-7b68dfdb46-tn42d 1/1 Running 0 22m 172.16.221.134 w1-k8s <none> <none> del-deploy-7b68dfdb46-w87b5 1/1 Running 0 22m 172.16.221.135 w1-k8s <none> <none> nginx-76d6c9b8c-hxrgl 1/1 Running 0 60s 172.16.132.12 w3-k8s <none> <none> nginx-76d6c9b8c-lnlwz 1/1 Running 0 104s 172.16.221.136 w1-k8s <none> <none> nginx-76d6c9b8c-nmvng 1/1 Running 0 60s 172.16.103.140 w2-k8s <none> <none> # 접속도 정상적으로 되는 것이 확인됨 [root@m-k8s ~]# curl 172.16.132.12 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> <style> html { color-scheme: light dark; } body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href="http://nginx.org/">nginx.org</a>.<br/> Commercial support is available at <a href="http://nginx.com/">nginx.com</a>.</p> <p><em>Thank you for using nginx.</em></p> </body> </html> # kubelet 시작 [root@m-k8s ~]# systemctl start kubelet # pod를 확인해보면 스케줄러가 다시 Running 상태인 것이 확인됨 [root@m-k8s ~]# kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE calico-kube-controllers-6856fc6d6c-w7zd5 1/1 Running 0 31m calico-node-bghzp 1/1 Running 0 2d1h calico-node-n7hnn 1/1 Running 0 2d calico-node-qntqg 1/1 Running 0 2d calico-node-tb9w4 1/1 Running 0 2d coredns-565d847f94-89zmp 1/1 Running 0 37s coredns-565d847f94-ws86r 1/1 Running 0 37s etcd-m-k8s 1/1 Running 0 2d1h kube-apiserver-m-k8s 1/1 Running 0 2d1h kube-controller-manager-m-k8s 1/1 Running 0 2d1h kube-proxy-cph5z 1/1 Running 0 2d1h kube-proxy-crj82 1/1 Running 0 2d kube-proxy-dtwj7 1/1 Running 0 2d kube-proxy-wkkxt 1/1 Running 0 2d kube-scheduler-m-k8s 1/1 Running 0 35s

# ContainerD 중단 [root@m-k8s ~]# systemctl stop containerd # pod가 정상적으로 출력됨 [root@m-k8s ~]# kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE calico-kube-controllers-6856fc6d6c-w7zd5 1/1 Running 0 42m calico-node-bghzp 1/1 Running 0 2d1h calico-node-n7hnn 1/1 Running 0 2d1h calico-node-qntqg 1/1 Running 0 2d1h calico-node-tb9w4 1/1 Running 0 2d1h coredns-565d847f94-89zmp 1/1 Running 0 11m coredns-565d847f94-ws86r 1/1 Running 0 11m etcd-m-k8s 1/1 Running 0 2d1h kube-apiserver-m-k8s 1/1 Running 0 2d1h kube-controller-manager-m-k8s 1/1 Running 0 2d1h kube-proxy-cph5z 1/1 Running 0 2d1h kube-proxy-crj82 1/1 Running 0 2d1h kube-proxy-dtwj7 1/1 Running 0 2d1h kube-proxy-wkkxt 1/1 Running 0 2d1h kube-scheduler-m-k8s 1/1 Running 0 11m # nginx deployment 삭제 [root@m-k8s ~]# kubectl delete deployment nginx deployment.apps "nginx" deleted # API가 실제로 동작하기 때문에 정상적으로 deployment가 삭제됨 [root@m-k8s ~]# kubectl get pods NAME READY STATUS RESTARTS AGE del-deploy-7b68dfdb46-24zv4 1/1 Running 0 36m del-deploy-7b68dfdb46-6hhmx 1/1 Running 0 36m del-deploy-7b68dfdb46-7jdlz 1/1 Running 0 36m del-deploy-7b68dfdb46-9h6ph 1/1 Running 0 36m del-deploy-7b68dfdb46-9ztks 1/1 Running 0 36m del-deploy-7b68dfdb46-m2f5d 1/1 Running 0 36m del-deploy-7b68dfdb46-pxvrm 1/1 Running 0 36m del-deploy-7b68dfdb46-tn42d 1/1 Running 0 36m del-deploy-7b68dfdb46-w87b5 1/1 Running 0 36m # nginx deployment 삭제 [root@m-k8s ~]# kubectl create deployment nginx --image=nginx deployment.apps/nginx created # API가 실제로 동작하기 때문에 정상적으로 deployment가 배포됨 [root@m-k8s ~]# kubectl get pods NAME READY STATUS RESTARTS AGE del-deploy-7b68dfdb46-24zv4 1/1 Running 0 37m del-deploy-7b68dfdb46-6hhmx 1/1 Running 0 37m del-deploy-7b68dfdb46-7jdlz 1/1 Running 0 37m del-deploy-7b68dfdb46-9h6ph 1/1 Running 0 37m del-deploy-7b68dfdb46-9ztks 1/1 Running 0 37m del-deploy-7b68dfdb46-m2f5d 1/1 Running 0 37m del-deploy-7b68dfdb46-pxvrm 1/1 Running 0 37m del-deploy-7b68dfdb46-tn42d 1/1 Running 0 37m del-deploy-7b68dfdb46-w87b5 1/1 Running 0 37m nginx-76d6c9b8c-k5gsl 0/1 ContainerCreating 0 2s # 스케줄러 삭제 시 프롬프트가 떨어지지 않고 멈춰있음 [root@m-k8s ~]# kubectl delete pod kube-scheduler-m-k8s -n kube-system pod "kube-scheduler-m-k8s" deleted ^c # 런타임에 문제가 생겼기 때문에 전달하기도, 전달받지도 못하는 상태이기 때문에 # Terminating 이라고 뜨지만 실제로 Terminagting 되지도 않고 다시 살아나지도 않음 [root@m-k8s ~]# kubectl get pod -n kube-system NAME READY STATUS RESTARTS AGE calico-kube-controllers-6856fc6d6c-w7zd5 1/1 Running 0 67m calico-node-bghzp 1/1 Running 0 2d1h calico-node-n7hnn 1/1 Running 0 2d1h calico-node-qntqg 1/1 Running 0 2d1h calico-node-tb9w4 1/1 Running 0 2d1h coredns-565d847f94-89zmp 1/1 Running 0 36m coredns-565d847f94-ws86r 1/1 Running 0 36m etcd-m-k8s 1/1 Running 0 2d1h kube-apiserver-m-k8s 1/1 Running 0 2d1h kube-controller-manager-m-k8s 1/1 Running 0 2d1h kube-proxy-cph5z 1/1 Running 0 2d1h kube-proxy-crj82 1/1 Running 0 2d1h kube-proxy-dtwj7 1/1 Running 0 2d1h kube-proxy-wkkxt 1/1 Running 0 2d1h kube-scheduler-m-k8s 1/1 Terminating 0 36m # ContainerD 재시작 [root@m-k8s ~]# systemctl start containerd # 스케줄러가 다시 Running으로 돌아옴 [root@m-k8s ~]# kubectl get pod -n kube-system NAME READY STATUS RESTARTS AGE calico-kube-controllers-6856fc6d6c-w7zd5 1/1 Running 0 69m calico-node-bghzp 1/1 Running 0 2d1h calico-node-n7hnn 1/1 Running 0 2d1h calico-node-qntqg 1/1 Running 0 2d1h calico-node-tb9w4 1/1 Running 0 2d1h coredns-565d847f94-89zmp 1/1 Running 0 38m coredns-565d847f94-ws86r 1/1 Running 0 38m etcd-m-k8s 1/1 Running 0 2d1h kube-apiserver-m-k8s 1/1 Running 0 2d1h kube-controller-manager-m-k8s 1/1 Running 0 2d1h kube-proxy-cph5z 1/1 Running 0 2d1h kube-proxy-crj82 1/1 Running 0 2d1h kube-proxy-dtwj7 1/1 Running 0 2d1h kube-proxy-wkkxt 1/1 Running 0 2d1h kube-scheduler-m-k8s 1/1 Running 0 38m