From 4921231311c8ae1add9abf2491746d382cec10f4 Mon Sep 17 00:00:00 2001 From: dingo Date: Wed, 21 Oct 2026 18:55:33 -0400 Subject: [PATCH] deploy(argocd): let the dev project carry ConfigMaps 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 --- deploy/argocd/dev/project.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deploy/argocd/dev/project.yaml b/deploy/argocd/dev/project.yaml index d9602c4..9355e84 100644 --- a/deploy/argocd/dev/project.yaml +++ b/deploy/argocd/dev/project.yaml @@ -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}