chore: temp-defer oauth2-proxy to break the prod-cert deadlock (re-enable after)

This commit is contained in:
jakman85 committed 2026-08-24 22:42:19 -05:00
1 parent ae3a0d7fd7
commit fc62345f0d
2 files changed
+10 -3

No files matched your search

+6 -1
View File
@@ -29,7 +29,12 @@ resources:
# Cluster CRs + ServiceMonitors + HTTPRoutes are in platform-config (dependsOn platform). ----
- cnpg # CloudNativePG operator (DB backend for Keycloak) — ghcr.io images (not Bitnami)
- keycloak # Keycloak Operator (quay.io images) + SOPS admin credential
- oauth2-proxy # forward-auth for non-OIDC UIs — SOPS oauth2-proxy-credentials now provisioned
# TEMP-DEFERRED (PM): oauth2-proxy sits in platform-core but depends on cert-manager's wildcard cert
# being LE-PROD-trusted (+ split-horizon DNS). While it's Failed, platform wait:true stays not-Ready,
# so platform-config can't reconcile the Certificate onto the prod issuer → deadlock. Deferring lets
# the prod cert issue; then re-enable so oauth2-proxy starts trusted. FOLLOW-UP: move oauth2-proxy to
# a post-platform tier (dependsOn platform-config) so it can never block its own dependencies.
# - oauth2-proxy # forward-auth for non-OIDC UIs (re-enable after wildcard cert is LE-prod)
# ---- Later phases: enabled when their phase opens ----
# - velero # Phase 4 (Backup/DR): BLOCKED on OQ-BKP (off-cluster backup target decision)
# - image-automation # Phase 4 (Automated updates): Flux image-automation + Renovate