Argo-CD 2.4 has a cool feature to exec into the Kubernetes Pod right from Argo CD Web UI!

In order to enable this feature, you need to add exec.enable: true in argo-cd helm chart values.yml

https://github.com/argoproj/argo-helm/blob/768907653a45ab5c65eb21c9b435857351eaf8a9/charts/argo-cd/values.yaml#L1236

I deploy argo-cd to AWS EKS cluster with terraform helm_release resource.

resource "helm_release" "argocd" {name             = "argocd"
create_namespace = "false"
chart            = "argo-cd"
namespace        = "argocd"
version          = "4.9.10"
repository       = "https://argoproj.github.io/argo-helm"set {
name  = "server.service.type"
value = "NodePort"
}set {
name  = "server.config.exec\\.enabled"
value = "true"
type  = "string"
}set {
name  = "server.extraArgs"
value = "{--insecure,--request-timeout=\"5m\"}"
}

The terminal will work for admin user only by default. If you have other users, you must allow them to access the terminal in their policy. See https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#exec-resource for details. Otherwise, users will get:
Terminal Connection Error: Internal Error

If this post was helpful, please click the clap 👏 button below a few times to show your support for the author 👇

🚀Developers: Learn and grow by keeping up with what matters, JOIN FAUN.