You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating an umbrella (wrapper) helm chart to deploy argocd and use the overrideNamespace attribute in values the redis-secret is created to the default namespace and not in the defined one. This makes all pods except the applicationset one unable to start. They return an error redis-secret not found
Describe the bug
When creating an umbrella (wrapper) helm chart to deploy argocd and use the
overrideNamespace
attribute in values theredis-secret
is created to the default namespace and not in the defined one. This makes all pods except theapplicationset
one unable to start. They return an errorredis-secret not found
Related helm chart
argo-cd
Helm chart version
7.3.4
To Reproduce
Create an umbrella chart like this
Chart.yaml
values.yaml
Expected behavior
To create the
redis-secret
in the defined namespace, so the pods can access it.Screenshots
No response
Additional context
What I did was to change locally the following lines:
argo-helm/charts/argo-cd/templates/redis-secret-init/job.yaml
Line 6 in 6dab549
argo-helm/charts/argo-cd/templates/redis-secret-init/role.yaml
Line 11 in 6dab549
argo-helm/charts/argo-cd/templates/redis-secret-init/rolebinding.yaml
Line 11 in 6dab549
argo-helm/charts/argo-cd/templates/redis-secret-init/serviceaccount.yaml
Line 7 in 6dab549
and replace them with the following:
Then I used this modified version of argo-cd chart to build my umbrella chart and everything was deployed correctly without errors.
Shall I create a PR to commit these changes or it is not the proper way to do it?
The text was updated successfully, but these errors were encountered: