Why is my application still
OutOfSync immediately after a successful Sync?
See Diffing documentation for reasons resources can be OutOfSync, and ways to configure Argo CD to ignore fields when differences are expected.
Why is my application stuck in
Argo CD provides health for several standard Kubernetes types. The
StatefulSet types have known issues which might cause health check
Progressing state instead of
Ingressis considered healthy if
status.loadBalancer.ingresslist is non-empty, with at least one value for
IP. Some ingress controllers (contour, traefik) don't update
status.loadBalancer.ingressfield which causes
Ingressto stuck in
StatufulSetis considered healthy if value of
status.updatedReplicasfield matches to
spec.replicasfield. Due to Kubernetes bug kubernetes/kubernetes#68573 the
status.updatedReplicasis not populated. So unless you run Kubernetes version which include the fix kubernetes/kubernetes#67570
StatefulSetmight stay in
As workaround Argo CD allows providing health check customization which overrides default behavior.
I forgot the admin password, how do I reset it?
argocd-secret secret and update the
admin.password field with a new bcrypt hash. You
can use a site like https://www.browserling.com/tools/bcrypt to generate a new hash. Another option
is to delete both the
admin.passwordMtime keys and restart argocd-server.