The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
A-8 — 롤링 재시작 증거
2026-09-04 13:38–13:41 KST
해설: docs/experiment-a8-rolling-restart.md
| 파일 | 무엇을 보여주는가 |
|---|---|
01-restart-availability.txt |
재시작 전 로그인(sid 기록), 롤링 재시작 중 외부 진입점 9회 모두 200 |
02-session-survival.txt |
재시작 전 토큰으로 refresh 200, DB 행 생존(last_session_refresh 갱신 확인), 세션 수 151 → 151, 캐시 0으로 초기화, 파드 나이 44초/66초 |
a8-cache-reset-cluster-reformed.png |
Grafana — 세션 캐시가 0 으로 떨어지고 cluster_size 가 다시 2 가 되는 구간 |
핵심 세 줄
- 무중단이었다. 한 번에 하나씩 내리고 readiness 가 전환을 맞춰준다 — replica ≥ 2 가 전제.
- 세션은 살아남고 캐시만 사라진다. DB 151건 그대로, 재시작 전 토큰이 그대로 통한다.
- 이것이
persistent-user-sessions를 켜는 진짜 이유다. A-7(volatile)에서 정반대가 나와야 한다.