argocd cluster add cannot add a cluster through the proxy-url of kubeconfig

[ilanni2460]

argocd version: 2.2.3

kubeconfig config:
`
apiVersion: v1
clusters:

• cluster:
  proxy-url: http://192.168.254.176:3128
  server: https://10.20.10.10:6443
  ...
  `

argocd cluster add cannot add a cluster through the proxy-url of kubeconfig

this is error log:

argocd cluster add c4135f4aa85864 --kubeconfig prod-k8s-admin --name prod -y
INFO[0000] ServiceAccount "argocd-manager" created in namespace "kube-system"
INFO[0000] ClusterRole "argocd-manager-role" created
INFO[0000] ClusterRoleBinding "argocd-manager-role-binding" created
FATA[0030] rpc error: code = Unknown desc = Get "https://10.20.10.10:6443/version?timeout=32s": dial tcp 10.20.10.10:6443: i/o timeout

[philippart]

Same issue here.

[manuelstein]

same here

[weaselchops]

Does anybody have a workaround for this in the meantime?

[chetan-rns]

argocd cluster add c4135f4aa85864 --kubeconfig prod-k8s-admin --name prod -y
INFO[0000] ServiceAccount "argocd-manager" created in namespace "kube-system"
INFO[0000] ClusterRole "argocd-manager-role" created
INFO[0000] ClusterRoleBinding "argocd-manager-role-binding" created
FATA[0030] rpc error: code = Unknown desc = Get "https://10.20.10.10:6443/version?timeout=32s": dial tcp 10.20.10.10:6443: i/o timeout

There could be 2 different clusters involved here. The target cluster we want to add and the cluster where argocd is running. Looking at the logs argocd creates the RBAC resources in the target cluster through the proxy. I suppose it's failing to talk to the argocd server. Here the proxy-url in the kubeconfig applies only to the target cluster.

[dinpau]

I think this problem is related to #6043, which is also open. We tried to give an analysis there, maybe it helps in this case too.

[jinnjwu]

same issue: #7887

[qixiaobo]

Same here