-
Notifications
You must be signed in to change notification settings - Fork 323
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]: Support for Kubernetes 1.14 #212
Comments
Note that 1.13 will need to be supported prior to 1.14, as Kubernetes masters need to be upgraded from minor to minor version (can't do a direct upgrade from 1.12 to 1.14). |
Issue #30 for 1.13 is in the "We're working on it" column @geerlingguy. |
Seems like we will need to wait a bit, there is no v1.13 yet, and v1.14 was release a long time ago... |
1.14 Kustomize is very useful, we really appreciated if 1.14 this could be shipped soon |
It looks AWS/EKS is being more informative about release timings. 🎉 This AWS blog article suggests 1.14 will be not be available before September 2019, So about 6 months after it went GA. It looks like from my reading of the article the plan is to stay at that ~6 months behind GA for future versions. https://aws.amazon.com/blogs/compute/updates-to-amazon-eks-version-lifecycle/ |
cool, clarification is good, on that note, will NLB fixes be backported to 1.13? e.g. this one: kubernetes/kubernetes@f052146 |
I know supported versions and the lag between K8s GA and managed provider GA is discussed a lot here. Looking forward to 1.14, this is I think the state of play across a range of providers.
The lag following a k8s GA release varies from 1-6 months, roughly breaking down as:
|
Also, any chance for NLB TLS support? |
@pawelprazak we're not able to backport this into 1.14 upstream as it's a big set of feature changes. This will be available in 1.15 |
Thank you for the answer, it's unfortunate to wait so long, but I appreciate the confirmation. |
1.14 is now GA on Azure AKS |
Is there a way for people deploying fresh clusters to utilize 1.14 while others who want to upgrade wait? i.e. our team doesn't upgrade clusters, we just build new ones. |
1.14 appeared in the documentation but it's not available for new clusters nor for upgrades in our AWS accounts. |
Maybe it takes a bit?? Announcement: https://aws.amazon.com/about-aws/whats-new/2019/09/amazon-eks-now-supports-kubernetes-version-1-14/ |
Amazon Elastic Kubernetes Service (EKS) now supports Kubernetes version 1.14.6 for all clusters. Kubernetes version 1.14 highlights include stable support for Durable Local Storage Management and Pod Priority, as well as the beta launch of Pid Limiting. Learn more about Kubernetes version 1.14 in the Kubernetes project release notes. Learn more about the Kubernetes versions available for production workloads on Amazon EKS and how to update your cluster to version 1.14 in the EKS documentation. Notes:
|
Is there a timeline for availability of the Windows EKS node AMI? Currently appears the latest version is 1.11.5? |
Tell us about your request
Support for k8s 1.14 control plane and nodes
Which service(s) is this request for?
EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Keep EKS clusters running supported releases on k8s and maintain security compliance requirements. It is hard because the EKS product is not keeping up with the k8s release cycle.
Are you currently working around this issue?
Making do with 1.11.x, which is, so last year 😆, and is EOL now
in 10 daysthat 1.14goesis GA.Additional context
k8s 1.14 has been in beta release for about a month and
goeswent GAin 10 dayson 25 March. Given the lead times we are seeing on 1.11/1.12/1.13 it would be nice to think AWS has the resource to be at least be testing 1.14 already, so it can make its way to customers in a timely manner. But it is not currently on the road map.WhenNow 1.14comesis outon 25 March1.11 is not longer supported for security updates, unless AWS is promising to back-port all security patches, EKS users have only 10 days left to upgrade clusters from 1.11 to 1.12, which is not even available on EKS yet, to be on a supported release and maintain security compliance requirements.I understand and appreciate AWS is operating a rigorous and careful release process. And that that is takes time and provides the huge benefit of offering a reliable upgrade process and a stable platform. But this rigorous approach appears to need to start earlier for upcoming releases than it is right now.
So to be clear, I am not requesting 1.14 now. I am requesting to get started on 1.14 soon, so that customers can have it well before 1.17 is released in ~8-9 months (and 1.14 is EOL)
The text was updated successfully, but these errors were encountered: