DongHyeonkaandClaude Opus 5
4177fb6a48
Both pods go NotReady, the Service endpoint list empties and the front door returns 503, so adding Keycloak replicas buys nothing against database loss. The node holding the session in cache fails too, because a refresh writes LAST_SESSION_REFRESH. Recovery was automatic in about fifteen seconds with no restart, which is what readiness rather than liveness buys. The observability finding matters as much: up stayed at 1 through a total outage, so alerting on it would have caught nothing. kube-state-metrics is missing and pod readiness is therefore not recorded as a metric. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
11 lines
408 B
Plaintext
11 lines
408 B
Plaintext
pod/a2-probe condition met
|
|
keycloak-0=10.42.1.67 keycloak-1=10.42.0.35
|
|
|
|
=== [준비] 양쪽 노드에 세션을 하나씩 만든다 ===
|
|
keycloak-0 에서 로그인 sid=EAXV5HcG2J1BZ3vnwONf64AQ 토큰길이=613
|
|
keycloak-1 에서 로그인 sid=McyTj5lj3n_JqApCXeuAHExc 토큰길이=613
|
|
|
|
=== [확인] 세션이 각자 노드에만 캐시되었는가 ===
|
|
keycloak-1 = 0 건
|
|
keycloak-0 = 1 건
|