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>
63 lines
2.3 KiB
YAML
63 lines
2.3 KiB
YAML
# Restrict who may reach the echo pods.
|
|
#
|
|
# Traefik is configured to trust X-Forwarded-* from the whole pod CIDR, and the
|
|
# app's Tomcat valve trusts every private range by default. Both are IP-range
|
|
# decisions, so any pod in the cluster can forge those headers by talking to the
|
|
# Service directly and bypassing Traefik entirely. Measured, not hypothetical:
|
|
#
|
|
# kubectl -n header-lab run t --rm -i --restart=Never --image=curlimages/curl -- \
|
|
# curl -s http://echo:8081/api/echo -H 'X-Forwarded-Host: evil.example.com'
|
|
# → serverName evil.example.com, remoteAddr 1.2.3.4
|
|
#
|
|
# A NetworkPolicy closes that path. It selects by label rather than IP, so it
|
|
# survives pod restarts and rescheduling — unlike the trustedIPs list, which
|
|
# could not name Traefik because its IP changes.
|
|
#
|
|
# "Trusting forwarded headers" and "guaranteeing a proxy sits in front" are a
|
|
# pair. Doing only the first leaves this hole.
|
|
apiVersion: networking.k8s.io/v1
|
|
kind: NetworkPolicy
|
|
metadata:
|
|
name: echo-allow-traefik-only
|
|
namespace: header-lab
|
|
spec:
|
|
podSelector:
|
|
matchLabels:
|
|
app: echo
|
|
policyTypes:
|
|
- Ingress
|
|
ingress:
|
|
# The proxy itself. namespaceSelector and podSelector in one list item are
|
|
# ANDed, so this is "traefik pods in kube-system" and nothing else.
|
|
- from:
|
|
- namespaceSelector:
|
|
matchLabels:
|
|
kubernetes.io/metadata.name: kube-system
|
|
podSelector:
|
|
matchLabels:
|
|
app.kubernetes.io/name: traefik
|
|
ports:
|
|
- protocol: TCP
|
|
port: 8081
|
|
|
|
# kubelet readiness/liveness probes originate from the node, not from a pod,
|
|
# so they need their own rule. Without it the probes fail and the pods are
|
|
# restarted in a loop.
|
|
#
|
|
# The probe's source address is the node's flannel bridge (cni0), which
|
|
# holds the first address of that node's /24:
|
|
# kc-lab-1 10.42.0.1 kc-lab-2 10.42.1.1
|
|
# Listing them as /32 keeps this rule from re-admitting arbitrary pods,
|
|
# which a broader 10.42.0.0/16 block would do and would undo the policy.
|
|
#
|
|
# Adding a node means adding its gateway here. Verify with:
|
|
# kubectl get nodes -o jsonpath='{range .items[*]}{.spec.podCIDR}{"\n"}{end}'
|
|
- from:
|
|
- ipBlock:
|
|
cidr: 10.42.0.1/32
|
|
- ipBlock:
|
|
cidr: 10.42.1.1/32
|
|
ports:
|
|
- protocol: TCP
|
|
port: 8081
|