-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support client.authentication.k8s.io/v1 #7596
Comments
Would you like to submit a PR for this? |
What version of Kubernetes are you using? If you are using an older version, you may also need to use an older version of workflows. |
Happy to submit a PR but wasn't quite sure how to generate the changes. Is it mostly running Re client version, I think my kubectl should be okay:
|
Trying
Hm |
Hi @aschleck, I had the same issue. |
We will need argo-events to update to k8s 1.22 before we can upgrade argo-workflows to 1.22. I filed argoproj/argo-events#1607 to get that started. |
is this solved @blkperl ? |
@tooptoop4 I'm not sure, if the new version of Kubernetes was all that was required then yes. |
Summary
Mirroring argoproj/argo-rollouts#1741,
argo
cli 3.2.6 doesn't support kubeconfig auth token plugins using versionclient.authentication.k8s.io/v1
What happened/what you expected to happen?
when my plugin outputs
I expected this to work fine.
What version of Argo Workflows are you running?
3.2.6
Diagnostics
Have a kubeconfig that uses a v1 auth plugin, then run any argo workflow command that uses a kubeconfig:
argo list --completed --since 7d
Thank you for your work on this project!
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: