DongHyeonkaandClaude Opus 5
8f6d67df35
Disabling persistent-user-sessions moves the session from PostgreSQL into the cluster, and the A-1 and A-8 outcomes flip to 400 Session not active while a new login during database loss starts working. The control group in each case still returns 200, so the injections cut only what they were meant to cut. This is the pair that makes the A layer legible: the conventional wisdom that sessions ride TCP 7800 is correct for Keycloak 24 and earlier, and the mistake is applying it to 26 without checking the version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
13 lines
500 B
Plaintext
13 lines
500 B
Plaintext
=== persistent 모드로 원복 ===
|
|
statefulset.apps/keycloak configured
|
|
partitioned roll out complete: 2 new pods have been updated...
|
|
|
|
=== [검증] persistent 로 돌아왔는가 — 로그인 후 DB 에 행이 생기는가 ===
|
|
["start"]
|
|
로그인
|
|
DB 온라인 세션: 1 건 (1 이면 persistent 복귀)
|
|
keycloak-0 1/1 Running 0 67s
|
|
keycloak-1 1/1 Running 0 89s
|
|
postgres-7b474b88c8-t6rrf 1/1 Running 0 2m8s
|
|
외부 진입점 HTTP 200
|