-
Notifications
You must be signed in to change notification settings - Fork 206
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
[FEATURE] Support EKS 1.22 #350
Comments
I tried testing this out myself but ran into problems with CDK. Unfortunately CDK's lambda-layer-kubectl is not yet compatible with EKS/Kubernetes v1.22, so as of right now CDK has had to rollback support for v1.22. See aws/aws-cdk#20000 for more info. |
release date of eks 1.22 is April 4, 2022, 1.23 is planned for August, but we still can not upgrade using cdk |
do we have any updates on this? @aceat64 |
seems like there is not much progress on this |
@nthienan @shcherbak CDK has removed support for EKS 1.22 so there is not much we can do on the blueprints side at the moment. The https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_eks.KubernetesVersion.html in CDK goes up to 1.21 at the moment (1.22 was removed due to compatibility issues). We are looking to escalate this issue with the CDK team. It is more involved than just adding version support. |
@shapirov103 I see this PR was merged, any news for cdk-eks-blueprints? |
Indeed, it only took half a year to address the PR. However, while it is merged, it is not released yet. Here is the actual released docs for 2.47. You can see there is no latest EKS versions in the list. I expected the next release 2.48 to happen by end of this week to include it. Then we can test the blueprints. |
EKS 1.23 is supported by CDK 2.49.0. Hope this be resolved soon! |
@shapirov103 hope we will have release to cover CDK 2.49.0 soon ^^ |
@vumdao working on it. |
This issue is resolved. I will keep it open for a bit to allow testing. Will close it out shortly. |
Supporting 1.23 and 1.24 atm. closing. |
No description provided.
The text was updated successfully, but these errors were encountered: