jakman85andClaude Opus 4.8
5fb097d019
Add Headlamp (kubernetes-sigs/headlamp Helm chart) at headlamp.home.keithjackson.dev with native Keycloak OIDC login and PER-USER RBAC: Headlamp forwards each user's id_token to the k3s apiserver, so the existing oidc:* group bindings (platform-admins->cluster-admin, viewers->view) apply per user. The ServiceAccount is deliberately NOT bound to cluster-admin (clusterRoleBinding.create=false), since user requests ride the forwarded token. Key integration nuance: the apiserver is configured oidc-client-id=kubernetes, so it only accepts tokens whose aud contains `kubernetes`. The new `headlamp` Keycloak client carries an oidc-audience-mapper (included.client.audience= kubernetes) so tokens carry aud=[headlamp, kubernetes] -- accepted by both Headlamp's own verifier and the apiserver, leaving the apiserver config untouched. A groups mapper emits the `groups` claim the apiserver maps to RBAC. - platform/headlamp: namespace, HelmRepository/HelmRelease, SOPS OIDC secret (externalSecret envFrom), default-deny NetworkPolicy + Cilium ingress (gateway)/egress (apiserver+Keycloak) policies, README. Wired into platform/kustomization.yaml (platform tier). - platform/headlamp/httproute.yaml wired into platform-config (Gateway API CR, dependsOn platform), modeled on grafana-httproute. - keycloak-realm-import: add `headlamp` confidential client + groups/audience mappers + HEADLAMP_CLIENT_SECRET placeholder. Client also created LIVE via kcadm (realm import no-ops on the existing realm). - keycloak-realm-clients.sops: add headlamp-client-secret (mirrored into headlamp-oidc-credentials clientSecret). Both encrypted to the repo age key. Co-Authored-By: Claude Opus 4.8 <[email protected]>
41 lines
2.3 KiB
Plaintext
41 lines
2.3 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
|