Onboard Crafty Controller (Minecraft panel) with Keycloak-gated web UI

Add Crafty Controller 4 (registry.gitlab.com/crafty-controller/crafty-4:4.10.8)
as a platform component: a web panel that runs Java + Bedrock Minecraft servers as
subprocesses in one pod + a 20Gi Longhorn PVC (mounted 5x by subPath).

Auth = Option B (per-app oauth2-proxy reverse-proxy sidecar), since Cilium 1.16.5
cannot do ext_authz on the shared Gateway:
- oauth2-proxy v7.8.1 sidecar (:4180) reverse-proxies to Crafty's self-signed HTTPS
  UI (127.0.0.1:8443), gated to Keycloak homelab realm group platform-admins.
- Confidential `crafty` client provisioned live via kcadm + captured in the realm
  import; client secret + cookie secret via SOPS/age (mirrored in realm-clients).

- Web UI: HTTPRoute crafty.home.keithjackson.dev -> Service :80 -> sidecar :4180.
- Game ports: Cilium L2 LoadBalancer on VIP 192.168.1.55 (next free after .53/.54),
  starter set TCP 25565-25567 (Java) + UDP 19132-19134 (Bedrock), NOT auth-gated.
- fsGroup:0 / runAsGroup:0 / runAsUser:1000 for the image's crafty:root identity on
  the root:root Longhorn PVC (the seerr fsGroup lesson).
- Own non-gating Flux tier clusters/base/crafty.yaml (dependsOn platform-config,
  wait:false) + sops-decryption patch in clusters/dev — a leaf UI must never gate
  the platform.
- Explicit default-deny NetworkPolicy + CiliumNetworkPolicies (platform namespace,
  not app-namespace, so Kyverno does not auto-generate the baseline).

make -C ci gate green; kustomize build of platform/crafty, clusters/base,
clusters/dev clean.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

platform/crafty/pvc.yaml

@@ -0,0 +1,25 @@
+---
+# Crafty data PVC (R-STATE-01/02) — the SINGLE stateful volume behind Crafty Controller. Crafty runs
+# every Minecraft server it creates as a SUBPROCESS inside its own container, so all server worlds,
+# backups, imports, logs and Crafty's own SQLite config/DB live under /crafty and must persist across
+# pod restarts. This one Longhorn RWO volume is mounted five times by subPath (deployment.yaml) to the
+# exact directories Crafty's docker-compose maps (/crafty/servers, /crafty/backups, /crafty/logs,
+# /crafty/import, /crafty/app/config).
+#
+# Sized 20Gi for a starter set of small worlds + rolling backups; expand via the Longhorn
+# allowVolumeExpansion storage class when real worlds grow. Replicated on the Longhorn 3-replica tier
+# (docs/04). fsGroup/root-group ownership so the non-root `crafty` user can write — see deployment.yaml.
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: crafty-data
+  namespace: crafty
+  labels:
+    app.kubernetes.io/name: crafty
+spec:
+  accessModes:
+    - ReadWriteOnce
+  storageClassName: longhorn
+  resources:
+    requests:
+      storage: 20Gi