argo-cd: Exec in apps outside of ArgoCD namespace not working

Together with the 2.5.0 update I deployed all ArgoCD apps apart from ArgoCD itself to their respective namespaces. When I want to exec into an ArgoCD pod everything works as usual. However when I try to exec into a pod in a different namespace I receive the error Terminal Connection Error: Internal error.

My policy.csv

p, admin, exec, create, */*, allow
g, group-name, admin

Checking the RBAC permissions for the argocd-server serviceaccount everything also looks good.

kubectl auth can-i create pods --subresource='exec' --as=system:serviceaccount:argocd:argocd-server
yes

The logs unfortunately don’t print anything useful.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 7
  • Comments: 15

Commits related to this issue

Most upvoted comments

@quentinlacrouts thanks for the nudge! I’ll get it merged today.

Are there any updates? 😃 I would really dislike having to revert all apps to the ArgoCD namespace due to this bug.

@yevgeniyo can you open a new issue for that? This one is specific to apps outside argocd.

it was my misconfiguration, sorry. we occasionally moved to HA cluster and there are need to patch ClusterRole instead of Role

Same here, web terminal stopped work for us after the upgrade to 2.5