Replies: 1 comment
-
|
@elysweyr Since this is about Argo CD itself, you can get more help in upstream. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am currently trying to debug an issue on my cluster-scope Argo CD instance. After a sync it seems that all applications are vanished from the UI (not deleted from k8s itself but not detected by Argo CD anymore).
I've exec'ed into the
argocd-serverpod and logged in as admin.argocd@cluster-argocd-server-5b64c8449d-dxvrs:~$ argocd app list NAME CLUSTER NAMESPACE PROJECT STATUS HEALTH SYNCPOLICY CONDITIONS REPO PATH TARGETThe CLI commands shows the same behavior even though apps are already present and its namespaces are managed by Argo CD.
This confirms that the following namespaces are watched for updates:
Let's list the Argo CD applications of
cluster-bootstrap.Let's confirm the configured permissions:
Argo CD's logs aren't much of a help either ...
In addition to that I've invalidated the cluster cache via the UI and restarted all pods multiple times. I've even re-installed this Argo CD instance but nothing changed. Argo CD is managing the relevant namespace but still not picking app the Argo CD apps even though the permissions have been correctly set up.
Any ideas what I should check next? Atm I'm quite clueless.
Edit:
I've performed some additional checks in order to confirm that lacking privileges aren't the root cause.
❯ kubectl auth can-i get app/self-bootstrapping -n cluster-bootstrap --as=system:serviceaccount:cluster-argocd:cluster-argocd-argocd-application-controller yes ❯ kubectl auth can-i get app -n cluster-bootstrap --as=system:serviceaccount:cluster-argocd:cluster-argocd-argocd-application-controller yes ❯ kubectl auth can-i list app -n cluster-bootstrap --as=system:serviceaccount:cluster-argocd:cluster-argocd-argocd-application-controller yes ❯ kubectl get sa -n cluster-argocd NAME SECRETS AGE cluster-argocd-argocd-application-controller 0 7m12s cluster-argocd-argocd-redis 0 7m12s cluster-argocd-argocd-redis-ha 0 7m12s cluster-argocd-argocd-server 0 7m12s default ❯ kubectl auth can-i get ns --as=system:serviceaccount:cluster-argocd:cluster-argocd-argocd-application-controller Warning: resource 'namespaces' is not namespace scoped yesEdit 2:
I've enabled debug logging on the application controller. Deleting and re-applying an app inside of a managed namespace hardly produces any logs.
Beta Was this translation helpful? Give feedback.
All reactions