Skip to content

Supported Version Policy #508

Open
Open
@praseedasathaye

Description

@praseedasathaye

Describe the problem

  1. In the https://aws.github.io/aws-eks-best-practices/upgrades/#keep-your-cluster-up-to-date under section "Supported Version Policy — Aligned with the Kubernetes community, Amazon EKS typically provides three active Kubernetes versions while deprecating a fourth version each year."

However in our documentation we say we support 4 versions. https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html

  1. Also the link in this paragraph is not working
    Auto-Upgrade Policy — We strongly recommend staying in sync with Kubernetes updates in your EKS cluster. Kubernetes community support, including bug fixes and security patches, typically ceases for versions older than one year. Deprecated versions may also lack vulnerability reporting, posing a potential risk. Failure to proactively upgrade before a version's end-of-life triggers an automatic upgrade, which could disrupt your workloads and systems. For additional information, consult the EKS Version Support Policy.

  2. This list has to be updated as well on this page. Its better not to keep the version links on this page
    For specific EKS version upgrade guidance, review the documentation for notable changes and considerations for each version.

EKS 1.27
EKS 1.26
EKS 1.25
EKS 1.24
EKS 1.23
EKS 1.22

  1. The link in this paragraph is also not working.
    The VPC CNI Metrics Helper may be used to create a CloudWatch dashboard for VPC metrics. Amazon EKS recommends updating the cluster subnets using the "UpdateClusterConfiguration" API prior to beginning a Kubernetes version upgrade if you are running out of IP addresses in the subnets initially specified during cluster creation. Please verify that the new subnets you will be provided:

References
https://aws.github.io/aws-eks-best-practices/upgrades/#keep-your-cluster-up-to-date

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions