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.
Argo CD cannot deploy Helm Chart based applications without internet access, how can I solve it?
Argo CD might fail to generate Helm chart manifests if the chart has dependencies located in external repositories. To solve the problem you need to make sure that
uses only internally available Helm repositories. Even if the chart uses only dependencies from internal repos Helm might decide to refresh
stable repo. As workaround override
stable repo URL in
argocd-cm config map:
data: helm.repositories: | - url: http://<internal-helm-repo-host>:8080 name: stable
I've configured cluster secret but it does not show up in CLI/UI, how do I fix it?
Check if cluster secret has
argocd.argoproj.io/secret-type: cluster label. If secret has the label but the cluster is still not visible then make sure it might be a
permission issue. Try to list clusters using
admin user (e.g.
argocd login --username admin && argocd cluster list).
Argo CD is unable to connect to my cluster, how do I troubleshoot it?
Use the following steps to reconstruct configured cluster config and connect to your cluster manually using kubectl:
kubectl exec -it <argocd-pod-name> bash # ssh into any argocd server pod argocd-util kubeconfig https://<cluster-url> /tmp/config --namespace argocd # generate your cluster config KUBECONFIG=/tmp/config kubectl get pods # test connection manually
Now you can manually verify that cluster is accessible from the Argo CD pod.