Killer Shell CKA - Apiserver Crash

1 개요

killercoda CKA - Apiserver Crash

Kubernetes의 kube-apiserver 매니페스트에 의도적으로 잘못된 인자를 추가하거나 YAML 문법 오류를 넣어 장애 상황을 만드는 실습

controlplane:~$ kubectl get pod -A | grep apiserver
NAMESPACE            NAME                                      READY   STATUS    RESTARTS      AGE
kube-system          calico-kube-controllers-fdf5f5495-8jbqm   1/1     Running   1 (14m ago)   30d
kube-system          canal-rtfc5                               2/2     Running   2 (14m ago)   30d
kube-system          coredns-6ff97d97f9-2rxsf                  1/1     Running   1 (14m ago)   30d
kube-system          coredns-6ff97d97f9-85m5c                  1/1     Running   1 (14m ago)   30d
kube-system          etcd-controlplane                         1/1     Running   1 (14m ago)   30d
kube-system          kube-apiserver-controlplane               1/1     Running   1 (14m ago)   30d
kube-system          kube-controller-manager-controlplane      1/1     Running   1 (14m ago)   30d
kube-system          kube-proxy-7kdz8                          1/1     Running   1 (14m ago)   30d
kube-system          kube-scheduler-controlplane               1/1     Running   1 (14m ago)   30d
local-path-storage   local-path-provisioner-5c94487ccb-gmwjg   1/1     Running   1 (14m ago)   30d

kube-apiserver를 Crash 시키기 위해 매니페스트 파일(/etc/kubernetes/manifests/kube-apiserver.yaml)에 잘못된 인수를 추가한다.

# 일단 백업!
cp /etc/kubernetes/manifests/kube-apiserver.yaml ~/kube-apiserver.yaml.ori

# 수정
vim /etc/kubernetes/manifests/kube-apiserver.yaml

# - --etcd-servers=https://127.0.0.1:2379
- --etcd-servers=this-is-very-wrong

controlplane:~$ k -n kube-system get pod
The connection to the server 172.30.1.2:6443 was refused - did you specify the right host or port?

2 같이 보기

killercoda CKA

3 참고

https://killercoda.com/killer-shell-cka/scenario/apiserver-crash