ArgoCD CLI with external redis

[AnhQKatalon]

Hello all,

Currently, I am using ArgoCD with an external Redis (AWS ElastiCache). All is good except the argocd command to communicate with the ArgoCD.

I would like to execute the following command
argocd admin cluster stats -n argo

But it return the following error

cannot find pod with selector: [app.kubernetes.io/name=argocd-redis-ha-haproxy app.kubernetes.io/name=argocd-redis] - use the --{component}-name flag in this command or set the environmental variable (Refer to https://argo-cd.readthedocs.io/en/stable/user-guide/environment-variables), to change the Argo CD component name in the CLI

How can I specify the --redis-name parameter in this case?

Thank you so much for all your helps

[jgwest]

Taking a peak at the code, you may be able to specify ---port-forward-redis false (the error message linked above is from port forward logic), then redis config params.

See these params from argocd admin cluster stats --help:

[jgw@localhost-lan dist]$ argocd admin cluster stats --help | grep -i "redis"
      --port-forward-redis                    Automatically port-forward ha proxy redis from current namespace? (default true)
      --redis string                          Redis server hostname and port (e.g. argocd-redis:6379). 
      --redis-ca-certificate string           Path to Redis server CA certificate (e.g. /etc/certs/redis/ca.crt). If not specified, system trusted CAs will be used for server certificate validation.
      --redis-client-certificate string       Path to Redis client certificate (e.g. /etc/certs/redis/client.crt).
      --redis-client-key string               Path to Redis client key (e.g. /etc/certs/redis/client.crt).
      --redis-insecure-skip-tls-verify        Skip Redis server certificate validation.
      --redis-use-tls                         Use TLS when connecting to Redis. 
      --redisdb int                           Redis database.
      --sentinel stringArray                  Redis sentinel hostname and port (e.g. argocd-redis-ha-announce-0:6379). 
      --sentinelmaster string                 Redis sentinel master group name. (default "master")

[varkey]

@AnhQKatalon Could you please share more details of your ElastiCache setup? Is it a multi node replication group with clustermode off?

[laurivosandi]

With external Redis the CLI is pretty much useless

$ argocd admin cluster stats --port-forward-redis false
{"level":"fatal","msg":"cannot find ready pod with selector: [app.kubernetes.io/name=argocd-redis-ha-haproxy app.kubernetes.io/name=argocd-redis] - use the --{component}-name flag in this command or set the environmental variable (Refer to https://argo-cd.readthedocs.io/en/stable/user-guide/environment-variables), to change the Argo CD component name in the CLI","time":"2026-03-05T23:36:10+02:00"}

$ argocd admin cluster stats 
{"level":"fatal","msg":"cannot find ready pod with selector: [app.kubernetes.io/name=argocd-redis-ha-haproxy app.kubernetes.io/name=argocd-redis] - use the --{component}-name flag in this command or set the environmental variable (Refer to https://argo-cd.readthedocs.io/en/stable/user-guide/environment-variables), to change the Argo CD component name in the CLI","time":"2026-03-05T23:36:20+02:00"}

$ argocd cluster add admin@ee-north-1.codemowers.io
WARNING: This will create a service account `argocd-manager` on the cluster referenced by context `admin@ee-north-1.codemowers.io` with full cluster level privileges. Do you want to continue [y/N]? y
{"level":"info","msg":"ServiceAccount \"argocd-manager\" already exists in namespace \"kube-system\"","time":"2026-03-05T23:36:31+02:00"}
{"level":"info","msg":"ClusterRole \"argocd-manager-role\" updated","time":"2026-03-05T23:36:31+02:00"}
{"level":"info","msg":"ClusterRoleBinding \"argocd-manager-role-binding\" updated","time":"2026-03-05T23:36:31+02:00"}
{"level":"info","msg":"Using existing bearer token secret \"argocd-manager-long-lived-token\" for ServiceAccount \"argocd-manager\"","time":"2026-03-05T23:36:31+02:00"}
{"grpc.code":"Unknown","grpc.component":"server","grpc.error":"error setting cluster info in cache: cannot find ready pod with selector: [app.kubernetes.io/name=argocd-redis-ha-haproxy app.kubernetes.io/name=argocd-redis] - use the --{component}-name flag in this command or set the environmental variable (Refer to https://argo-cd.readthedocs.io/en/stable/user-guide/environment-variables), to change the Argo CD component name in the CLI","grpc.method":"Create","grpc.method_type":"unary","grpc.service":"cluster.ClusterService","grpc.start_time":"2026-03-05T23:36:32+02:00","grpc.time_ms":"151.661","level":"error","msg":"finished call","peer.address":"127.0.0.1:58538","protocol":"grpc","time":"2026-03-05T23:36:32+02:00"}
{"level":"fatal","msg":"rpc error: code = Unknown desc = error setting cluster info in cache: cannot find ready pod with selector: [app.kubernetes.io/name=argocd-redis-ha-haproxy app.kubernetes.io/name=argocd-redis] - use the --{component}-name flag in this command or set the environmental variable (Refer to https://argo-cd.readthedocs.io/en/stable/user-guide/environment-variables), to change the Argo CD component name in the CLI","time":"2026-03-05T23:36:32+02:00"}

I use DragonflyDB to setup redis and I can't set labels.

I actually find it quite odd that CLI hits directly Redis..