Containers-roadmap: [EKS]: Support For Kubernetes 1.18

[marcincuber]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
Support Kubernetes 1.18

Which service(s) is this request for?
EKS

[gudipatiharitha]

Hi , could you please let us know the planned date for avaibility of this task in AWS, we need to plan our deployment based on that , we have a dependancy on CSI proxy for windows added in 1.18. Thank you

[abdennour]

Also we have a dependency on startupProbe which is beta feature in 1.18
https://github.com/aws/containers-roadmap/issues/947

[mikhailjan]

We could really use the HorizontalPodAutoscaler behaviour functionality that was added in the v1.18 v2beta2 API. https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-configurable-scaling-behavior.

[stijndehaes]

For those who didn't see it yet, the EKS documentation now contains a release calendar with future releases in it:
https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#kubernetes-release-calendar

[limewxr]

When can we know the exact release date of EKS 1.18? 😁

[lwimmer]

When can we know the exact release date of EKS 1.18?

When it is released :grimacing:

[mikestef9]

Kubernetes version 1.18 is now available on EKS!

Documentation
What's New
eksctl support

[groodt]

Upgraded our clusters to this today! Thanks! Smooth so far!

One issue we saw during the upgrade:

It is advised to use CoreDNS 1.7.0 in the docs.

When doing so, we got CrashLoopBackoff due to:

plugin/kubernetes: /etc/coredns/Corefile:6 - Error during parsing: unknown property 'upstream'

So we rolled back to 1.6.6 and everything is working. Is this a documentation issue?

[gitfool]

@groodt looks like it. (I filed #1115 after it failed for me too.)