`argocd login --core` is using local cli instead the API server

[liranZiv27]

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.
• [x] I've pasted the output of argocd version.

Describe the bug

We have a management argocd instance, which deploys apps to "worker" clusters. When using the argocd cli to log into the argocd instance with the --core flag, all commands that need access to the worker clusters fail with this error, which doesn't appear in any logs, therefore the assumption it's executed using kubectl locally -

time="2024-08-21T10:03:44Z" level=fatal msg="rpc error: code = Unknown desc = error validating and updating app: error validating and normalizing app: error validating the repo: error getting k8s server version: Get \"https://*****************.eks.amazonaws.com/version?timeout=32s\": getting credentials: exec: executable argocd-k8s-auth not found%0A%0AIt looks like you are trying to use a client-go credential plugin that is not installed.%0A%0ATo learn more about this feature, consult the documentation available at:%0A      https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins"

Worker clusters are authenticated and have workloads deployed.

To Reproduce

• Cluster 'B' connected to your Argocd instance 'A'
• Have an app deployed on cluster 'B'
• Run these argocd commands:

  argocd login $ARGOCD_URL --core
  argocd app set app-staging \
  --grpc-web --server $ARGOCD_URL --core \
  --source-position 1 \
  --helm-set service.image.tag='v1.0.0'
  OR
  argocd app diff app-staging --revision <git-hash> --core

Expected behavior

Running argocd app set deploys the specified version

Version

argocd: v2.12.1+26b2039
  BuildDate: 2024-08-16T18:33:39Z
  GitCommit: 26b2039a55b9bdf807a70d344af8ade5171d3d39
  GitTreeState: clean
  GoVersion: go1.22.6
  Compiler: gc
  Platform: darwin/arm64

Logs

Paste any relevant application logs here.

[felfa01]

Ran into this issue as well with argocd app set. Works fine when modifying Applications with destination local to the current context but throws error when modifying Applications with external destinations.

A workaround for me is using kubectl patch Application , but I'd rather use the ArgoCD cli.