-
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
Kubectl in ubuntu20-20220503.1 breaks EKS integration #5493
Comments
We have updated kubectl version to 1.24.0. Looks like it is a known issue - kubernetes/kubectl#1210 https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md#deprecation
As a workaround you can rollback to 1.23.6:
or use task:
|
Thanks for the quick response. I went with the former set of sudo commands in ADO pipelines to fudge the version in the image and it worked. Suspect this is going to cause a storm, so is there any chance of downgrading the version of Kubectl in the image or is there a way to explicitly request the previous tag of ubuntu-latest as part of the vm-image directive? |
Great to see this being sorted so quickly! Is there an Azure DevOps Pipelines equivalent to that task? |
A task would be nice. However, I've done the following for now: /pipelines/jobs/downgrade_kubectl.yaml:
then in each of your jobs (joy!):
|
An ADO supported root level spec would be best yeah but in the meantime that's going to unblock us by the looks of things so thanks! |
Thanks for the workaround. Had pipeline failures out of nowhere. |
I can confirm that this also happens to Ubuntu 18.04. |
Hi! I can confirm that in GitHub actions it is not working, we have the same issue with the "ubuntu-20.04" or the latest version. Many thanks! |
Now that aws-cli has resolved the issue on their end, it seems like the problem is that the Github hosted runners are running on stale images. |
I've encountered the same issue with azure/setup-helm@v1 |
Close as external - aws/aws-cli#6920 |
Description
When trying to use kubectl to communicate with AWS EKS, it reports the following:
error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"
I can't follow the Kubectl version numbers. The previous image used Kubectl v1.23.6, this new one uses Kubectl 4.5.4?
Issue is similar to this: https://www.reddit.com/r/k8s/comments/ui46zf/deploying_on_eks_cia_travis_ci_fails/
Virtual environments affected
Image version and build link
No public example
Is it regression?
No response
Expected behavior
Kubectl authentication should work.
Actual behavior
Kubectl authentication does not work.
Repro steps
Try using kubectl to communicate with an EKS cluster in any way.
The text was updated successfully, but these errors were encountered: