deploy(argocd): let the dev project carry ConfigMaps
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m27s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 4s
Foundation / server-image (push) Successful in 4s

The rules-12 tuning file reaches the provision Job as a kustomize-generated
ConfigMap, which the dev AppProject refused ("ConfigMap is not permitted in
project aevolution-dev"), so the region-10 sync failed validation and applied
nothing. ConfigMaps carry only Git-managed, non-secret configuration; stage and
world0 projects already allow them. Projects are applied by hand.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-21 18:55:33 -04:00
co-authored by Claude Opus 5.5
parent 1222e8bcf4
commit 4921231311
+3 -1
View File
@@ -1,7 +1,8 @@
# M8.4 dev workload project (replaces deploy/argocd/project.yaml.example). Apply by hand
# (kubectl apply -f deploy/argocd/dev/project.yaml): Argo CD does not manage its own
# projects here. One namespace, no cluster kinds; ServiceAccounts only for the
# foundation proof Job (the platform owns the environment's service accounts).
# foundation proof Job (the platform owns the environment's service accounts). ConfigMaps
# carry only Git-managed, non-secret configuration such as the rules-12 tuning file.
apiVersion: argoproj.io/v1alpha1
kind: AppProject
metadata:
@@ -16,6 +17,7 @@ spec:
namespace: evolution-dev
clusterResourceWhitelist: []
namespaceResourceWhitelist:
- {group: "", kind: ConfigMap}
- {group: "", kind: ServiceAccount}
- {group: "", kind: Service}
- {group: apps, kind: Deployment}