Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
(aws-eks): Make sure kubectl is compatible with the k8s version
See original GitHub issueCurrently, to update Kubernetes resources, we use kubectl version 1.20, hardcoded in a lambda layer. For now, this works fine, but eventually, as new Kubernetes versions are released, they won’t be compatible with the client anymore. Also, it’s not an option to always use the latest version of the client, as we know that kubectl version 1.21.0 is not compatible with version 1.20 (and lower) of the server.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:13
- Comments:16 (5 by maintainers)
Top Results From Across the Web
Updating an Amazon EKS cluster Kubernetes version
Before updating your control plane to a new Kubernetes version, make sure that the Kubernetes minor version of both the managed nodes and...
Read more >Best Practices for Upgrading Amazon EKS Clusters - Rafay
As a best practice, make sure you test the behavior of your apps against new versions of Kubernetes before you update your production ......
Read more >kube-apiserver - Kubernetes
The API version of the authentication.k8s.io TokenReview to send to ... The purpose of this format is make sure you have the opportunity...
Read more >AWS EKS - Get available Kubernetes versions - Stack Overflow
I guess it would be a fair assumption that all available K8s versions in EKS would be compatible with some add-on or the...
Read more >The Right Kubectl Version for Each Kubernetes Cluster
How many different Kubernetes clusters and versions do you need to work with? ... of kubectl and related tools, so you can be...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Really seems crazy there’s nothing on the roadmap for this yet.
Is there a status update on this? Any reason why there can’t be a different layer version per EKS version? AWS only supports a given EKS version for 16 months. 1.20 is end of support in approximately 3 months. Due to the rolling nature of EKS, CDK needs to support matching versions for kubectl. Once 1.20 is EOS, the control plane will automatically migrate to the next supported version breaking the use of kubectl either way.