Supported Environments

Please review the information listed below to understand the supported versions.

---

Kubernetes Versions

The following versions of Kubernetes are currently supported. New EKS clusters can be provisioned using the following Kubernetes versions. Existing EKS clusters managed by the controller can be upgraded in-place to the following Kubernetes versions.

Important

Customers are strongly recommended to upgrade their EKS clusters to a recent supported version to ensure they continue to receive patches and security updates.

Kubernetes Version	End of Standard Support	Extended Support	'New Cluster Provisioning' & 'Convert to Managed' support added with Controller release version	'In-place upgrade' support added with Controller release version
v1.31.x	26 Nov 2025	26 Nov 2026	v2.10 Update 1	v2.10 Update 1
v1.30.x	23 July 2025	23 July 2026	v2.7	v2.7
v1.29.x	23 Mar 2025	23 Mar 2026	v2.4	v2.4
v1.28.x	26 Nov 2024	26 Nov 2025	v2.1	v2.1 Update 1
v1.27.x	24 Jul 2024	24 Jul 2025	v1.27 Update 1	v2.0
v1.26.x	11 Jun 2024	11 Jun 2025	v1.25 Update 1	v1.27
v1.25.x	01 May 2024	01 May 2025	v1.25	v1.25
v1.24.x	31 Jan 2024	31 Jan 2025	v1.22	v1.22
v1.23.x	11 Oct 2023	11 Oct 2024	v1.21	v1.21

Important

• From Kubernetes version 1.30 and later, Amazon EKS no longer applies the default annotation to the gp2 StorageClass resource for newly created clusters. This adjustment does not affect users who reference this storage class by its name. However, if you were depending on having a default StorageClass in your cluster, you will need to take action. It is recommended that you reference the StorageClass explicitly by the name gp2.

• For new cluster creation from version 1.30 onward, you can deploy Amazon EBS with default storage class settings. Specifically, you can enable the defaultStorageClass.enabled parameter by setting it to true when installing aws-ebs-csi-driver add-on. This will create a StorageClass with the default annotation. With this configuration, if your application deployment code utilizes the default annotation, it will continue to function without requiring modifications to your application deployment automation. You can include this configuration in the EBS CSI managed add-on section of the Rafay cluster configuration, as shown below.

  ---
  addons:
  - name: coredns
  version: v1.11.1-eksbuild.8
  - name: vpc-cni
  version: v1.18.1-eksbuild.3
  - name: kube-proxy
  version: v1.30.0-eksbuild.3
  - name: aws-ebs-csi-driver
  version: v1.35.0-eksbuild.1
  configurationValues: |-
      {
          "defaultStorageClass": {
          "enabled": true
          }
      }
  

For more information about these changes, please refer to the AWS documentation for Kubernetes 1.30.

---