'argocd version --client' fails if no valid Kubernetes context after using 'argocd login --core' #7426
Open
3 tasks done
Labels
bug
Something isn't working
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Checklist:
argocd version
.Describe the bug
After logging into an Argo CD instance running in an EKS cluster with
argocd login --core
, I can no longer runargocd version --client
without having a valid Kubernetes context to the EKS cluster.The assumption is that
argocd version --client
would not require access to the Kubernetes API at all using--client
.To Reproduce
To successfully login with
--core
:Now, without any Kube context:
Or with an invalid/expired (using assumed IAM Role tokens) Kube context for the EKS cluster:
Expected behavior
argocd version --client
to return theargocd
version regardless of Kubernetes context.Version
The text was updated successfully, but these errors were encountered: