-
Notifications
You must be signed in to change notification settings - Fork 321
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
[EKS]: Kubernetes v1.11 End of Support (Nov 4, 2019) #464
Comments
Is there any possibility of the Windows preview being updated to a more recent version? At the moment I'm stuck using 1.11 purely because of this. |
…wo latest versions Replacing 1.10 and 1.11, which are both deprecated: - aws/containers-roadmap#300 - aws/containers-roadmap#464 Output from acceptance testing: ``` --- PASS: TestAccAWSEksCluster_Version (2292.24s) ```
So, didn't really fully appreciate the significance of this - in that clusters will be automatically upgraded from 1.11 to 1.12 on November 4th. So what is the plan for those of us currently running clusters on 1.11 to participate in the Windows nodes preview? |
To quote @mikestef9's reply in #69
|
@dcopestake Windows GA has been launched |
Amazing, thanks @mikestef9! |
I noticed EKS 1.11 creation of clusters nor auto-upgrade has taken effect? Any ETA when this will happen? |
Hi team, From this date Do we have any information about it, so we can prepare? |
We will announce the deprecation of v1.12 when we launch support for v1.15. From that announcement, you will have 60 days to upgrade existing 1.12 clusters before automatic updates start rolling out. |
In line with the Kubernetes community support for Kubernetes versions, Amazon EKS 1.11 is now deprecated and will no longer be supported on Nov 4, 2019. On this day, you will no longer be able to create new 1.11 clusters and all EKS clusters running Kubernetes version 1.11 will be updated to the latest available platform version of Kubernetes version 1.12.
We recommend customers upgrade existing 1.11 or 1.12 clusters and worker nodes to at least 1.13 as soon as practical.
Learn more:
The text was updated successfully, but these errors were encountered: