Skip to content
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

Upgrade API VERSION from client.authentication.k8s.io/v1alpha1 to client.authentication.k8s.io/v1beta1 #1020

Closed
mmerkes opened this issue Sep 14, 2022 · 1 comment

Comments

@mmerkes
Copy link
Member

mmerkes commented Sep 14, 2022

What would you like to be added

Upgrade the API version from client.authentication.k8s.io/v1alpha1 to client.authentication.k8s.io/v1beta1. The API version is referenced here and used by the aws-iam-authenticator version currently used in the AMI - 0.5.0. More details below.

Why is this needed

The alpha API version is no longer supported in Kubernetes version 1.24.

aws-iam-authenticator Note

This change requires upgrading the aws-iam-authenticator to 0.5.9 or any version with this commit. After upgrading the API version, you'll see the following error if the aws-iam-authenticator is not upgraded as well:

getting credentials: exec plugin is configured to use API version client.authentication.k8s.io/v1beta1, plugin returned version client.authentication.k8s.io/v1alpha1

If you're building your own AMI and not vending the aws-iam-authenticator from the EKS buckets, you'll need to update it. As of 9/14/2022, the 0.5.0 authenticator is stored in the binary buckets, but we'll update that as part of resolving this issue.

Future Improvement:

This PR makes a change that would allow us to remove the dependency on the aws-iam-authenticator entirely by using the AWS CLI to call aws eks get-token instead of calling the authenticator. However, as of 9/14/2022, the AmazonLinux yum repos use an older version of the AWS CLI that doesn't include this change, which is required for resolving this issue. Once the CLI is updated, we should be able to remove the dependency altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants