-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
aws eks update-kubeconfig invalid apiVersion #6920
Comments
Hi @code-is-art thanks for reporting. We just received a feature request related to this: #6916. There is also a related PR open (#6476) that the team is going to prioritize reviewing. Are you able to pin to a previous version of Kubernetes as a temporary solution? |
yes v1.23.6 works fine. I modified my pipelines to stay at this version for now. I was doing curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl but now I am doing the following as a solution. curl -LO https://storage.googleapis.com/kubernetes-release/release/v1.23.6/bin/linux/amd64/kubectl I believe this version of kubectl was released yesterday and my new pipeline picked it up. |
https://gist.github.com/Zheaoli/335bba0ad0e49a214c61cbaaa1b20306 Here's the workround |
If you are still having issues in your pipeline or after you install make sure to check the version:
|
Still experiencing the same issue. |
Facing same issue |
same here |
1 similar comment
same here |
There is a thumbs up button on the first post for the |
same here |
I have the same problem with GitHub runner.
|
Even simply getting the kubectl version is showing this error: `➜ ~ sudo apt search kubectl kubetail/focal 1.6.5-2 all ➜ ~ kubectl version |
worked like a charm for us; thank you @TranToan2910 ! ❤️ |
|
same problem when using github actions ... |
Thanks all for your feedback. As someone mentioned earlier, please 👍 the original post if you are affected by this and only leave a comment if you have additional information to share. Kubernetes v1.24.0 was released Tuesday, May 3rd according to here: https://kubernetes.io/releases/ Several users have reported this breaking their workflows, many of which involve the use of GitHub Actions/Runners. The team is actively looking into this further and I will share an update as soon as I have more information. In the meantime, reverting to v1.23.6 is a temporary solution as mentioned in comments here and here. |
the aws-cli produces a kubeconfig that is incompatible with v1.24.x version of kubectl. see aws/aws-cli#6920 for more details
I am having issues with that action:
|
the aws-cli produces a kubeconfig that is incompatible with v1.24.x version of kubectl. see aws/aws-cli#6920 for more details
the aws-cli produces a kubeconfig that is incompatible with v1.24.x version of kubectl. see aws/aws-cli#6920 for more details
* the aws-cli produces a kubeconfig that is incompatible with v1.24.x version of kubectl. see aws/aws-cli#6920 for more details * Turn EKS integration tests back on
For MAC: First verify the version: Download and install 1.23.6: Fixed! |
Upgrade aws client version!!!!!! |
Consegui resolver da seguinte forma:
E funcionou. |
I have the samme issue: I'm using nevest aws version
And I'm using nevest to date kubectl when i switched v1alpha1 to v1beta1 it worked but is it a good workaround? |
For MacOS users still facing this issue, I upgraded the aws CLI version (from
and now copy-paste the AWS environment variables (short-term credentials) into the terminal session
|
Check kubectl config file: Copy current kubectl config
Reconfigure kubectl
Check if the issue exists: |
Got it working on
|
Same issue here. The min working version was 1.23 as well. |
Worked by upgrading the aws cli version: from 2.2.41 to 2.11.9 |
Same issue still exist when using kubectl client version: v1.24.x Still requires to downgrade to use client version v1.23.x for resolving the problem. |
Thanks @rahulbaid , worked for me |
Worked by upgrading the aws cli version: from 2.2.41 to 2.11.9 |
Thanks @rahulbaid! Worked for me, executing the second step session.
|
Try to update the kubeconfig with changing "apiVersion: client.authentication.k8s.io/v1alpha1" into "apiVersion: client.authentication.k8s.io/v1beta1" and it works for me. I think maybe it causes by the upgrade of the kubernetes apiVersion. |
Having the issue with latest aws-cli and latest kubectl. |
same issue. This worked for me:
|
Thankyou so much. This worked for me. |
apparent, this changed?? aws/aws-cli#6920 (comment)
This works with the newer version of kubectl, aws cli, eks and k8s - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_cluster#arn - aws cli install: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html - kubectl version: aws/aws-cli#6920 (comment) - - gravitational/teleport#23032 - https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html
This worked for me. |
This is to address aws/aws-cli#6920
But what about awscli v1 ? Since #4947 is still unresolved, many environments cannot install, much less update, awscli v2. Because No EKS for those, right? 😉 |
With:
— I got it working by downgrading kubectl to latest available version before 1.24.0 (kubectl dropped I.e. in Ubuntu, in my case, the latest version before 1.24.0 was 1.23.17:
|
This works for me |
Describe the bug
Update kubectl from v1.23.6 to 1.24.0 and run commands
I get the following error and exit status 1
Kubectl must need an updated apiVersion in kubeconfig file. Not sure if this is on aws side or kubectl side.
kubernetes/kubectl#1210
Expected Behavior
No error message when using
kubectl
andaws eks update-kubeconfig
Current Behavior
error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"
Reproduction Steps
Update kubectl from v1.23.6 to 1.24.0 and run commands
Possible Solution
No response
Additional Information/Context
No response
CLI version used
whatever is running in aws/codebuild/standard:5.0
Environment details (OS name and version, etc.)
aws/codebuild/standard:5.0
The text was updated successfully, but these errors were encountered: