From 4bcde12a2e972ad6eee943bc6f876a93df3e68db Mon Sep 17 00:00:00 2001 From: Sven Urbanski Date: Fri, 20 Sep 2024 10:10:27 +0200 Subject: [PATCH] chore: enable argo cd to use the development cluster in run-kind (#1969) This fixes the issue where the rollout-service could not communicate with argo cd (permission denied). It has actually nothing to do with permissions, the project was just misconfigured. Note that this fix is only for the development cluster. Ref: SRX-78FWXB --- charts/kuberpult/run-kind.sh | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/charts/kuberpult/run-kind.sh b/charts/kuberpult/run-kind.sh index e9f03454d..68b3a875a 100755 --- a/charts/kuberpult/run-kind.sh +++ b/charts/kuberpult/run-kind.sh @@ -220,6 +220,7 @@ $(sed -e "s/^/ /" <../../services/cd-service/known_hosts) policy.csv: | p, role:kuberpult, applications, get, */*, allow p, role:kuberpult, applications, create, */*, allow + p, role:kuberpult, applications, update, */*, allow p, role:kuberpult, applications, sync, */*, allow p, role:kuberpult, applications, delete, */*, allow g, kuberpult, role:kuberpult @@ -229,11 +230,13 @@ helm install argocd argo-cd/argo-cd --values argocd-values.yml --version 5.36.0 print applying app... +# For now, we are only creating development here +# This means argo cd will only handle development, including the rollout-status kubectl apply -f - <