kube-context CLI arg is ignored

[shamil]

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

I want to override current-context by using the --kube-context flag. But seems like argocd cli ignores it.

To Reproduce

The following command fails:

argocd --kube-context not-current-context --core app list

also even when I login with --core

atgocd login --core
argocd --kube-context not-current-context app list

I get the follwoing error

FATA[0000] invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable

When I change the current-context, everything works

kubectl config use-context not-current-context

Expected behavior

argocd cli should not ignore the --kube-context cli arg and properly override current-context

Version

argocd: v2.6.5+60104ac
  BuildDate: 2023-03-14T14:42:25Z
  GitCommit: 60104aca6faec73d10d57cb38245d47f4fb3146b
  GitTreeState: clean
  GoVersion: go1.18.10
  Compiler: gc
  Platform: linux/amd64

[mrsimo]

This would be really useful for us. We have a bunch of documentation with a scattering of # point your kubectl context to the right cluster comments, and it'd be so much easier to have --kube-context work as expected.

I don't know if this flag is intended for a different purpose, but having it be a global flag does make me expect it to work as described by the issue.

Big 👍🏻 !!

[prateekkhera92]

+1 for this bug fix. We have lots of clusters and scripts to manage them. This flag will ensure that scripts (using argocd cli) runs on correct clusters