Commit Graph
3 Commits
Author SHA1 Message Date
Sten d6a97a22df fix(apps): explicit forte-drop namespace (sync-wave -1, Prune=false)
AI Code Review / ai-review (pull_request) Successful in 1m40s
Codex review: the apps overlay applies namespaced resources
(keycloak-client Secrets, forte-drop-secrets, PDB) to forte-drop, but
no base created the namespace — first sync on a fresh cluster raced
ahead of the Applications' CreateNamespace and failed with
'namespaces forte-drop not found' until a retry.

Add an explicit Namespace at sync-wave -1 so it exists before the
wave-0 namespaced resources (covers both web + mcp bases via the
shared parent). Prune=false keeps removing a base from cascade-
deleting the namespace + postgres data + the other deployment.
2026-05-29 10:25:37 +02:00
Sten c4b7167f9e feat(apps): add forte-drop-secrets sealed secret
Sealed forte-drop-secrets with the real UpCloud Managed Object Storage
creds (existing drops bucket), PG creds matching the deployed
forte-drop-pg-creds, and PASSWORD_GATE_SECRET. Consumed by both web +
mcp deployments (envSecretName) and the pg-backup CronJob (S3 creds).
2026-05-29 10:03:57 +02:00
Sten 6bc5bd29b3 feat(apps): PodDisruptionBudget for forte-drop web (minAvailable 1) 2026-05-29 09:31:16 +02:00