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
It is not really a bug but I still struggle to find an elegant solution for the following problem and I am sure I just miss a point in the documentations somewhere 🤯
We use helmfile to deploy our apps. So I would also like to use it to deploy Argo.
Error: Unable to continue with install: ConfigMap "argocd-cmd-params-cm" in namespace "argocd" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "argocd": current value is "argocd-configmaps"
That is clear, the release names per se are different. Can't I tell the Argo Chart where to look for these config maps? I mean they are in the same namespace as the docs say.
Thank you for pointers.
Related helm chart
argo-cd
Helm chart version
7.1.4
To Reproduce
Take an empty chart. Use helmfile. Add a ConfigMap as 1 release and argocd as another.
Expected behavior
I'd expect I can set somewhere that it should not also verify the release name. Most people that create the ConfigMaps separate from the ArgoCD might use another release name no?
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Hi all,
It is not really a bug but I still struggle to find an elegant solution for the following problem and I am sure I just miss a point in the documentations somewhere 🤯
We use helmfile to deploy our apps. So I would also like to use it to deploy Argo.
But I struggle with this plain install:
The error naturally is:
That is clear, the release names per se are different. Can't I tell the Argo Chart where to look for these config maps? I mean they are in the same namespace as the docs say.
Thank you for pointers.
Related helm chart
argo-cd
Helm chart version
7.1.4
To Reproduce
Take an empty chart. Use helmfile. Add a ConfigMap as 1 release and argocd as another.
Expected behavior
I'd expect I can set somewhere that it should not also verify the release name. Most people that create the ConfigMaps separate from the ArgoCD might use another release name no?
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: