We are rolling out EKS v1.32. Please make sure to update to our recommended client versions matching this upgrade. This upgrade includes an important change in how PersistentVolumeClaims (PVCs) are handled by StatefulSets. When a StatefulSet is deleted, the PVCs created by the StatefulSet will now be automatically removed too. This is a change in behavior from previous versions of Kubernetes.
Timeline:
- Testing & rollout to non-production clusters has happened in the past days
- Production rollouts are expected to finish at the end of next week
- Update this changelog when everything is finished
Important changes between K8s 1.31 and 1.32
This following list is a selection of the most important changes in Kubernetes 1.32 from a user point of view:
- Auto remove PVCs created by StatefulSet: when a StatefulSet is deleted, the PVCs created by the StatefulSet will be automatically removed too. This is good news in terms of cleaning up resources, but it’s a change in behavior from previous versions to take into account. If your PersistentVolume Reclaim Policy is set to
Delete, this also means the PV and eg backed EBS volume will be deleted when the PVC is removed. Our default PV Reclaim Policy is set toRetain, so this will not affect you if you don’t change this setting specifically. - When a Pod encounters an
ImagePullBackOffthe status messages have been improved to be more human-friendly and more detailed.
For detailed info on what’s new and changed, please make sure to check the Kubernetes 1.32 release announcement and the full Kubernetes 1.32.x changelog.
EKS specific updates
AWS EKS 1.32 announcement blog and release notes.
In the process of upgrading EKS, we have also upgraded the following components:
- AWS EKS AMI to the latest version
v20250123 - Cluster Autoscaler to
v1.32.0 - Karpenter to
v1.2.1 - KubeProxy to
v1.32.0-eksbuild.2
Actions to take
There are no specific actions to take for you this release.