<p>Check out the eks versions faq at the bottom of <a href="https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html" rel="nofollow noreferrer">this page</a>:</p>
<blockquote>
<p>Q: What happens on the end of support date?</p>
<p>A: On the end of support date, [...]. Existing control planes are automatically updated by Amazon EKS to the earliest supported version through a gradual deployment process after the end of support date. [...]</p>
</blockquote>
<p>End of support date for 1.23 is October 11, 2023</p>
<p>Also about timing:</p>
<blockquote>
<p>Q: When exactly is my control plane automatically updated after the end of support date?</p>
<p>A: Amazon EKS can't provide specific time frames. Automatic updates can happen at any time after the end of support date.</p>
</blockquote>
<p>so you should do it yourself to keep control. Otherwise it could happen any time after the EOL date.</p>
<p>They also state why they do it like that:</p>
<blockquote>
<p>Q: Can I leave my control plane on a Kubernetes version indefinitely?</p>
<p>A: No. Cloud security at AWS is the highest priority. [...]</p>
</blockquote>
<p>But the worker nodes are under your domain</p>
<blockquote>
<p>Q: Are Amazon EKS managed node groups automatically updated along with the cluster control plane version?</p>
<p>A: No. A managed node group creates Amazon EC2 instances in your account. [...] The Kubernetes version that's on your managed node group might be more than one version earlier than your control plane. [...]</p>
</blockquote>
<p>so your dockershim use-cases should be save.</p>

CC BY-SA 4.0
2023-09-12T14:20:41.130Z
2023-09-12T14:20:41.130Z
Chris
<p>I'm desperately trying to resolve all of our dockershim uses so we can migrate to EKS 1.24+, but I'm not optimistic I'll get it done before the &quot;deadline&quot;.</p>
<p>I'm stuck on EKS 1.23 until I can replace DooD. I wonder what will happen when it's no longer supported in October?</p>

<kubernetes><amazon-web-services><eks>
What happens when you are running a "too old" version of k8s in eks?
Shanteva
# What happens when you are running a "too old" version of k8s in eks?

(Asked by: username_0 on 2023-09-08)

I'm desperately trying to resolve all of our dockershim uses so we can migrate to EKS 1.24+, but I'm not optimistic I'll get it done before the "deadline".

I'm stuck on EKS 1.23 until I can replace DooD. I wonder what will happen when it's no longer supported in October?

**Tags:** kubernetes, amazon-web-services, eks


---

## 1 answers

### Answer by username_1 on 2023-09-12. Score: 2 | Accepted answer

Check out the eks versions faq at the bottom of [this page](https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html):

> Q: What happens on the end of support date?
>
> A: On the end of support date, [...]. Existing control planes are automatically updated by Amazon EKS to the earliest supported version through a gradual deployment process after the end of support date. [...]

End of support date for 1.23 is October 11, 2023

Also about timing:

> Q: When exactly is my control plane automatically updated after the end of support date?
>
> A: Amazon EKS can't provide specific time frames. Automatic updates can happen at any time after the end of support date.

so you should do it yourself to keep control. Otherwise it could happen any time after the EOL date.

They also state why they do it like that:

> Q: Can I leave my control plane on a Kubernetes version indefinitely?
>
> A: No. Cloud security at AWS is the highest priority. [...]

But the worker nodes are under your domain

> Q: Are Amazon EKS managed node groups automatically updated along with the cluster control plane version?
>
> A: No. A managed node group creates Amazon EC2 instances in your account. [...] The Kubernetes version that's on your managed node group might be more than one version earlier than your control plane. [...]

so your dockershim use-cases should be save.


---

