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>
19 lines
916 B
Plaintext
19 lines
916 B
Plaintext
=== 새 postgres 가 Pending 인 이유 ===
|
|
Events:
|
|
Type Reason Age From Message
|
|
---- ------ ---- ---- -------
|
|
Warning FailedScheduling 4m45s default-scheduler 0/2 nodes are available: 1 node(s) didn't match PersistentVolume's node affinity, 1 node(s) had untolerated taint(s). no new claims to deallocate, preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
|
|
|
|
=== keycloak-0 대체 파드가 안 생기는 이유 (StatefulSet) ===
|
|
keycloak 2 <none> 1
|
|
keycloak-0 1/1 Terminating 0 30m
|
|
keycloak-1 0/1 Running 0 143m
|
|
|
|
=== 복구 — 노드 재기동 ===
|
|
재기동 시각: 12:16:31
|
|
Domain 'kc-lab-2' started
|
|
|
|
+30초 node=Ready | Running 파드 3 개 | 외부 HTTP 503
|
|
+60초 node=Ready | Running 파드 3 개 | 외부 HTTP 200
|
|
→ 서비스 복귀
|