v0.26.1
Planned updates to supported kubernetes versions
- Kubernetes 1.33 reaches end of standard support on August 31, 2026
- Extended support continues until August 31, 2027 for clusters with valid license tokens
- Clusters will continue to function but will not receive CVE patches or bug fixes after standard support ends
- Kubernetes 1.30 reaches end of extended support on August 31, 2026
- No further patches will be available after this date
- Existing clusters will continue to function but upgrading is strongly recommended
For complete version support details, see the Kubernetes version support table.
Supported OS version details
| vSphere | Bare Metal | Nutanix | Snow | |
|---|---|---|---|---|
| Ubuntu 22.04 | ✔ | ✔ | ✔ | ✔ |
| Ubuntu 24.04 | ✔ | ✔ | ✔ | — |
| Bottlerocket 1.64.0 | ✔ | — | — | — |
| RHEL 8.x | ✔ | ✔ | ✔ | — |
| RHEL 9.x | ✔ | ✔ | ✔ | — |
* Bottlerocket v1.64.0 applies to Kubernetes versions 1.33 through 1.36. Kubernetes versions 1.30 through 1.32 remain on Bottlerocket v1.62.0.
Added
redhat_epel_rpmandepel_rpm_gpg_keyimage-builder configuration options, allowing RHEL images to be built in networks that cannot reach the Fedora EPEL mirrors (#5632)
Changed
- EKS Distro:
- Bottlerocket (Kubernetes 1.33-1.36):
v1.62.0tov1.64.0(#5626) - Cluster API Provider AWS Snow (CAPAS):
v0.3.1tov0.3.3(#5606)
Fixed
- Fix registry mirror image pulls failing on Bottlerocket nodes running Kubernetes 1.33 and above, caused by a containerd v2 regression in Bottlerocket. Resolved by the Bottlerocket
v1.64.0bump (#5626) - Fix Tinkerbell binding address (#10921)
- Fix feature flags not propagating to the controller during an upgrade with no version difference (#10907)
- Fix MachineHealthCheck timeout duration overflow in v1beta2 conversion (#10874)
- Increase Tinkerbell node deletion timeout to 30s (#10906)