Skip to content

Release 2023-06-04
Compare
Choose a tag to compare
@phealy phealy released this 15 Jun 19:18
· 633 commits to master since this release
2023-06-04
f1ee688
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release 2023-06-04

Monitor the release status by regions at AKS-Release-Tracker.

Announcements

  • Docker container runtime for Windows nodepools has been retired as of May 1, 2023. You may remain on existing deployed instances but scaling operations will fail, nodepool creation will fail, and you will be out of support. Follow the detailed steps in our documentation to upgrade to containerd. In alignment with this retirement, AKS has deleted all published windows 2019 docker images.
  • After May 31, 2023, Ubuntu 18.04 will reach end of life. AKS will continue to update the host OS from Canonical into the Kubernetes 1.24 VHD images. Customers will not receive daily security updates from Canonical past the end of May, but will be able to consume those through a node image update only.
  • Each Kubernetes version is supported for 12 months. After 12 months, the minor version will shift to platform support only. Our new platform support policy provides customers with Azure infrastructure support while the cluster is in an n-3 version (where n is the latest supported AKS GA minor version). Platform support does not include anything related to Kubernetes functionality and components, but provides customers with additional support beyond what was previously provided for unsupported versions.
  • Unattended Upgrades are disabled on Azure Linux when running on a NVIDIA GPU enabled VM sizes.
  • SecurityPatch OS Servicing channel is not supported on Azure Linux when running on NVIDIA GPU enabled VM sizes.
  • Windows2019 will be retired in Kubernetes v1.33 and above (ETA March 2026). Customers should upgrade to Windows2022.

Release notes

  • Behavior Changes

    • Automatic upgrades will now be blocked on clusters that have clients using deprecated API versions. This will be logged into the cluster's activity log. Upgrades will be retried during each upgrade interval and will succeed when usage of deprecated APIs has stopped. Clusters can also be upgraded manually with the deprecated API validation bypassed.
    • Konnectivity will now be deployed into clusters using BYOCNI or API Server VNet Integration in combination with Azure CNI Overlay.

  • Component Updates

Assets 2
Loading