Looks like when using argocd in microshift 4.16 the configmap in charge of holding the authorized hosts of git repos "argocd-ssh-known-hosts-cm" is recreated when microshift is restarted.

microshift-4.16.13-202409171717.p0.g15ea7cd.assembly.4.16.13.el9.x86_64
microshift-gitops-1.12.1-4.el9.x86_64

Always

    1. edit cm: "oc -n openshift-gitops edit cm argocd-ssh-known-hosts-cm" and add new valid entry
    2. sudo systemctl restart microshift
    3. check again the cm: "oc -n openshift-gitops get cm argocd-ssh-known-hosts-cm -o yaml", new entry is gone
    

Checking again ArgoCD looks like the operator watches that the CM exists but not the content. This looks to be different with microshift reduced implementation, maybe this is not the way to set up this.

CM doesn't change upon microshift restart, or other method is specified to maintain this list.

It is pretty contradicting to read in the secrets of the file:

# This file was automatically generated by hack/update-ssh-known-hosts.sh. DO NOT EDIT

but also on the upstream doc we see that this is the way to add hosts:
https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#ssh-known-host-public-keys

Please clarify if that is not the way to do it, which is the correct way, or modify the message as it is misleading.