Open sreeniHari opened 3 months ago
As per @crenshaw-dev's original answer, if you want to continuously apply the Argo CD install manifests while maintaining your own settings, you should maintain your own fork of the install YAML (and rebase as needed to the latest version), or you should use a tool like kustomize
to apply your own customizations to the argocd-ssh-known-hosts-cm
ConfigMap
Checklist:
argocd version
.The argocd-ssh-known-hosts-cm config map is overwritten. I bootstrapped argocd using argo-helm. I am using app of app pattern on a private repo. The initial config for known host from values.yaml is correctly set during helm install and the private repo is successfully connected. Then almost immediately argocd-ssh-known-hosts-cm is overwritten with default known hosts values as per below hack script.
Related public discussion/posts in the past are below. Surprised that the issue is still relevant today.
https://github.com/argoproj/argo-cd/discussions/10035
https://stackoverflow.com/questions/76261186/argocd-fails-updating-bitbucket-org-private-repos-with-ssh-handshake-failed-k ( refer comment from kuskoman ) May 18, 2023 at 13:46
To Reproduce
Expectation
Persistence of changes done to argocd-ssh-known-hosts-cm be it CLI, GUI or modifying the cm directly.
Screenshots
Version
Logs