DongHyeonkaandClaude Opus 5
d0666c5ba0
Kubernetes keeps calling the node Ready for forty seconds while users already see failures, and the pod on the powered-off machine stays ready=true because its kubelet can no longer contradict itself. Eviction waits another five minutes, then the StatefulSet refuses to recreate its pod and the replacement Deployment pod cannot schedule because the local-path volume is pinned to the dead node. Killing the server node instead shows the opposite shape: containerd keeps the workload running while the API server, Traefik and the observability stack disappear, so the outage is the missing path rather than the missing application. Traefik at one replica is the ingress single point of failure. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
20 lines
1.3 KiB
Plaintext
20 lines
1.3 KiB
Plaintext
=== 컨트롤 플레인 노드(kc-lab-1) 전원 차단 ===
|
|
차단 시각: 12:18:08
|
|
Domain 'kc-lab-1' destroyed
|
|
|
|
|
|
+20초 외부 auth=000 grafana=000 | kubectl: Unable to connect to the server: dial tcp
|
|
+40초 외부 auth=000 grafana=000 | kubectl: Unable to connect to the server: dial tcp
|
|
+60초 외부 auth=000 grafana=000 | kubectl: Unable to connect to the server: dial tcp
|
|
+80초 외부 auth=000 grafana=000 | kubectl: Unable to connect to the server: dial tcp
|
|
+100초 외부 auth=000 grafana=000 | kubectl: Unable to connect to the server: dial tcp
|
|
+120초 외부 auth=000 grafana=502 | kubectl: Unable to connect to the server: dial tcp
|
|
+140초 외부 auth=000 grafana=000 | kubectl: Unable to connect to the server: dial tcp
|
|
+160초 외부 auth=000 grafana=000 | kubectl: Unable to connect to the server: dial tcp
|
|
|
|
=== 살아 있는 노드에서 직접 확인 — 워크로드는 도는가 ===
|
|
CONTAINER IMAGE CREATED STATE NAME ATTEMPT POD ID POD NAMESPACE
|
|
e5f777900b762 60e153026e8f5 4 minutes ago Running keycloak 0 640d4dafaefb3 keycloak-0 keycloak-lab
|
|
|
|
6
|