jakman85andClaude Opus 4.8
0437871807
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]>
43 lines
2.4 KiB
Plaintext
43 lines
2.4 KiB
Plaintext
# =============================================================================
|
|
# TEMPLATE — NOT APPLIED, NOT ENCRYPTED (.yaml.example is ignored by kustomize and never
|
|
# auto-encrypted by SOPS). Reference scaffold + OPERATOR HAND-OFF.
|
|
#
|
|
# WHAT THIS IS: the OIDC client secrets for the two confidential clients the realm import
|
|
# (keycloak-realm-import.yaml) provisions — grafana and oauth2-proxy. The realm import injects
|
|
# these values via spec.placeholders ($(env:GRAFANA_CLIENT_SECRET) / $(env:OAUTH2_PROXY_CLIENT_SECRET)),
|
|
# so the client secrets live ONLY here (SOPS-encrypted), never in the realm YAML (R-IDP-04; docs/07).
|
|
#
|
|
# HAND-OFF STEPS (operator):
|
|
# (a) Generate two client secrets:
|
|
# openssl rand -hex 32 # -> grafana-client-secret
|
|
# openssl rand -hex 32 # -> oauth2-proxy-client-secret
|
|
# (b) Copy to: platform/keycloak/keycloak-realm-clients.sops.yaml
|
|
# (c) Fill the two values below; encrypt:
|
|
# sops -e -i platform/keycloak/keycloak-realm-clients.sops.yaml
|
|
# (d) Add under `resources:` in platform/keycloak/kustomization.yaml:
|
|
# - keycloak-realm-clients.sops.yaml
|
|
# (e) THE SAME two values must also go into the CONSUMING apps' SOPS secrets so both sides match:
|
|
# - oauth2-proxy-client-secret -> platform/oauth2-proxy/oauth2-proxy-credentials.sops.yaml
|
|
# (key: client-secret) [oauth2-proxy namespace]
|
|
# - grafana-client-secret -> platform/monitoring/grafana-oidc-credentials.sops.yaml
|
|
# (key: client-secret) [monitoring namespace]
|
|
# - headlamp-client-secret -> platform/headlamp/headlamp-oidc-credentials.sops.yaml
|
|
# (key: clientSecret) [headlamp namespace]
|
|
# (Cross-namespace Secrets cannot be shared, hence one value stored in two encrypted files.)
|
|
#
|
|
# Until this file is filled + added to the kustomization, the KeycloakRealmImport stays PENDING
|
|
# (placeholder unresolved) — the documented bring-up gate for the SSO clients.
|
|
# =============================================================================
|
|
apiVersion: v1
|
|
kind: Secret
|
|
metadata:
|
|
name: keycloak-realm-clients
|
|
namespace: keycloak
|
|
type: Opaque
|
|
stringData:
|
|
grafana-client-secret: REPLACE-ME
|
|
oauth2-proxy-client-secret: REPLACE-ME
|
|
headlamp-client-secret: REPLACE-ME
|
|
# Mirror into platform/crafty/crafty-oauth2-proxy-credentials.sops.yaml (key: client-secret).
|
|
crafty-client-secret: REPLACE-ME
|