DongHyeonkaandClaude Opus 5
f45a2a2aaa
Stopping Redis returns HTTP 000 rather than an error because the client waits on reconnect, and the pod keeps serving traffic because the redis health indicator is not in the readiness group even though /actuator/health returns 503. That is the mirror image of A-2, where Keycloak put its database check in readiness and the pods left the Service. Turning on AOF with config set created the appendonlydir and still lost everything on pod deletion, because /data was the container filesystem; adding a PVC makes the same setting work. Volume first, persistence setting second. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
13 lines
407 B
Plaintext
13 lines
407 B
Plaintext
=== health 그룹별 응답 — 왜 파드는 Ready 인가 ===
|
|
/actuator/health HTTP server
|
|
/actuator/health/readiness HTTP 200
|
|
/actuator/health/liveness HTTP 200
|
|
|
|
=== /actuator/health 본문 (Redis 항목이 있는가) ===
|
|
|
|
|
|
=== /actuator/health/readiness 본문 ===
|
|
{"status":"UP"}
|
|
|
|
=== Service 엔드포인트 — 트래픽을 계속 받는가 ===
|
|
ready: [10.42.0.52 10.42.1.124] |