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] Mismatch between EKS AMI and Kubernetes version
See original GitHub issueDescribe the bug
The version for EKS is being selected based on what the hardcoded latest version is, in the codebase. Which is 1.11 source. However, specifying no version for EKS at all creates 1.12 based on what CloudFormation decides for you.
To Reproduce Create an EKS cluster and worker nodes without specifying any version.
Expected behavior I would like to see the same AMI being used as the Kubernetes version that CloudFormation is selecting for EKS.
Version:
- OS X
- Typescript
- CDK 0.33.0 (still the same in 0.35.0)
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I am leaning towards making the version explicit. Seems like any automatic selection of a version will result in non-deterministic behavior.
Duplicate #7762