Error while adding cluster via argocd login --core

[sabinayakc]

Checklist:

• [ X ] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [ X ] I've included steps to reproduce the bug.

Describe the bug

When adding a cluster using argocd cli and cluster context, I get the following error.

Command: kubectl config set-context --current --namespace=argocd argocd login --core argocd cluster add ${CLUSTER_TO_ADD} --name ${CLUSTER_NAME} -y

Output:

  time="2023-03-28T18:23:18Z" level=info msg="ServiceAccount \"argocd-manager\" created in namespace \"kube-system\""
  time="2023-03-28T18:23:18Z" level=info msg="ClusterRole \"argocd-manager-role\" created"
  time="2023-03-28T18:23:18Z" level=info msg="ClusterRoleBinding \"argocd-manager-role-binding\" created"
  time="2023-03-28T18:23:23Z" level=info msg="Created bearer token secret for ServiceAccount \"argocd-manager\""
  time="2023-03-28T18:23:25Z" level=error msg="finished unary call with code Unknown" error="cannot find pod with selector: [app.kubernetes.io/name=argocd-redis-ha-haproxy app.kubernetes.io/name=argocd-redis]" grpc.code=Unknown grpc.method=Create grpc.service=cluster.ClusterService grpc.start_time="2023-03-28T18:23:25Z" grpc.time_ms=366.762 span.kind=server system=grpc
  time="2023-03-28T18:23:25Z" level=fatal msg="rpc error: code = Unknown desc = cannot find pod with selector: [app.kubernetes.io/name=argocd-redis-ha-haproxy app.kubernetes.io/name=argocd-redis]"

To Reproduce

• Deploy argocd via Helm (v5.27.0) with HA in management cluster.
• Try adding a remote cluster to argocd CLI using KubeContext of the mangement cluster.

Expected behavior

• Cluster should be added with no error.

Version Helm: v5.27.0 ArgoCD: v2.6.5 EKS: 1.25

[todaywasawesome]

@sabinayakc Would you try the command again but add --grpc-web? I wouldn't think that it would fix it but for some reason it can't find the pods it's looking for.

[dtwilliamsWork]

I’m also getting this problem. It won’t create the argocd-manager service account on kube-system as it says unauthorised. I’m using EKS v1.25

Do I need to reconfigure any of the service accounts that Argo is using?

I’ve run “kubectl auth can-i create serviceaccount -n kube-system” which returns yes so assume it’s which account Argo is using that doesn’t have permissions??

[mtougeron]

This is probably related to https://github.com/argoproj/argo-cd/issues/12721

[s3than]

This issue is that the argocd cli hardcodes app.kubernetes.io/name and the helm chart uses app and has no way to add additional items in the subchart used for installing redis-ha

[s3than]

See https://github.com/argoproj/argo-cd/blob/master/common/common.go#L151

[vainkop]

argo-cd/charts/redis-ha/values.yaml

## Custom labels for the redis pod
labels:
  app.kubernetes.io/name: argocd-redis

  ## Custom labels for the haproxy pod
  labels:
    app.kubernetes.io/name: argocd-redis-ha-haproxy

[s3than]

Adding the label to the chart works.. though it would be nice to be able to pass the whole key/value instead