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
I have noticed that an upgrade of ArgoCD overwrites the configmap argocd-ssh-known-hosts-cm. This is a bit inconvenient when one has made custom changes, e.g. adding a SSH key for a private repo.
Motivation
This behaviour adds a repetitive additional step for each upgrading. Since it isn't needed to overwrite the configmap on upgrade, this should be handled differently.
Proposal
For now, the upgrade manifest is the same as the install-from-scratch manifest. Maybe it would just be sufficient to provide an upgrade-manifest which does not apply any configmaps.
The text was updated successfully, but these errors were encountered:
Summary
I have noticed that an upgrade of ArgoCD overwrites the configmap argocd-ssh-known-hosts-cm. This is a bit inconvenient when one has made custom changes, e.g. adding a SSH key for a private repo.
Motivation
This behaviour adds a repetitive additional step for each upgrading. Since it isn't needed to overwrite the configmap on upgrade, this should be handled differently.
Proposal
For now, the upgrade manifest is the same as the install-from-scratch manifest. Maybe it would just be sufficient to provide an upgrade-manifest which does not apply any configmaps.
The text was updated successfully, but these errors were encountered: