EKS Version Lag vs. Upstream Kubernetes

EKS Version Lag vs. Upstream Kubernetes A workflow diagram generated by Archify. 01 / Upstream Kubernetes 02 / Amazon EKS Kubernetes 1.33 Kubernetes 1.34 Kubernetes 1.35 Kubernetes 1.36 1.33 released · 2025-04 · Upstream Kubernetes › Kubernetes 1.33 1.33 released 2025-04 1.34 released · 2025-08 · Upstream Kubernetes › Kubernetes 1.34 1.34 released 2025-08 1.35 released · 2025-12 · Upstream Kubernetes › Kubernetes 1.35 1.35 released 2025-12 1.36 released · 2026-04 · Upstream Kubernetes › Kubernetes 1.36 1.36 released 2026-04 1.33 on EKS · EKS: May 2025 · Amazon EKS › Kubernetes 1.33 1.33 on EKS EKS: May 2025 1.34 on EKS · EKS: Oct 2025 · Amazon EKS › Kubernetes 1.34 1.34 on EKS EKS: Oct 2025 1.35 on EKS · EKS: Jan 2026 · Amazon EKS › Kubernetes 1.35 1.35 on EKS EKS: Jan 2026 1.36 on EKS · EKS: Jun 2026 · Amazon EKS › Kubernetes 1.36 · most recent 1.36 on EKS EKS: Jun 2026 most recent +4 months +4 months +4 months Legend Cloud service External system

Reading the Figure

  • • Top lane: upstream Kubernetes release month for 1.33 through 1.36
  • • Bottom lane: when the same version became available on Amazon EKS
  • • EKS availability lags the upstream release by about 1-2 months

What the Lag Buys

  • • Stability: AWS validates the release with EKS-specific integrations
  • • Add-on compatibility: managed add-ons are tested and updated
  • • AMI availability and security patches: optimized EKS AMIs are built and known CVEs are addressed before release