Default API version set in EKS update-kubeconfig to v1 #6923
Labels
customization
Issues related to CLI customizations (located in /awscli/customizations)
eks
eks-kubeconfig
feature-request
A feature should be added or improved.
p3
This is a minor priority issue
Comments
kyleknap
added
feature-request
tim-finnigan
added
eks-kubeconfig
eks
and removed
needs-triage
kdaily
added
the
customization
|
Just adding a note on this, we can't default to v1 until EKS no longer supports Kubernetes 1.21 (see table in #6940), which is probably about 18 months away (so ~Dec 2023), and v1beta1 will be supported until 1.29 which is projected to come out December 2023/ January 2024 upstream, and in EKS about 6 months after that. (Wow, I think this is the first time I've planned on doing something other than voting in 2024). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature
Tracking issue for setting the API version in the
~/.kube/configto v1 by default instead of v1alpha1 or v1beta1.Use Case
The API version v1alpha1 is no longer supported by the latest version of kubectl and v1beta1 will eventually be dropped as well.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CLI version used
v1 and v2
Environment details (OS name and version, etc.)
Any environment
The text was updated successfully, but these errors were encountered: