DongHyeonkaandClaude Opus 5
b2963105a8
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>
44 lines
1.8 KiB
YAML
44 lines
1.8 KiB
YAML
# Make Traefik trust the X-Forwarded-* headers that the host nginx sets.
|
|
#
|
|
# Without this, Traefik rewrites every forwarded header from its own connection,
|
|
# which is plain HTTP on port 80. The application then sees scheme=http even
|
|
# though the browser connected over TLS. See docs/two-hop-proxy-header-contract.md.
|
|
#
|
|
# k3s installs Traefik through its bundled HelmChart, so values are overridden
|
|
# with a HelmChartConfig rather than by editing the deployment. k3s reconciles
|
|
# the chart and recreates the Traefik pod.
|
|
#
|
|
# kubectl apply -f deploy/lab/k8s/traefik-forwarded-headers.yaml
|
|
# kubectl -n kube-system rollout status deploy/traefik --timeout=180s
|
|
apiVersion: helm.cattle.io/v1
|
|
kind: HelmChartConfig
|
|
metadata:
|
|
name: traefik
|
|
namespace: kube-system
|
|
spec:
|
|
valuesContent: |-
|
|
ports:
|
|
web:
|
|
forwardedHeaders:
|
|
# Requests arriving from these sources keep their existing
|
|
# X-Forwarded-* values instead of having them rewritten.
|
|
#
|
|
# 10.42.0.0/16 is the pod CIDR. It is required because the traefik
|
|
# Service uses externalTrafficPolicy: Cluster, so svclb SNATs the
|
|
# traffic and Traefik sees a pod-network address rather than the
|
|
# host nginx address.
|
|
#
|
|
# The node/host range is deliberately absent. Because svclb SNATs,
|
|
# the host nginx address never reaches Traefik — measured, not assumed.
|
|
# Trusting a range that cannot appear only widens the surface.
|
|
#
|
|
# Trusting the whole pod CIDR still means any pod in the cluster could
|
|
# forge these headers, which is why echo-network-policy.yaml restricts
|
|
# who may reach the application at all.
|
|
trustedIPs:
|
|
- 10.42.0.0/16
|
|
websecure:
|
|
forwardedHeaders:
|
|
trustedIPs:
|
|
- 10.42.0.0/16
|