3.9.7

Important

Due to REST API version changes, you cannot upgrade to MKE 3.9 directly from MKE 3.8.10 or earlier. Upgrade in the following order:

  1. Upgrade to MKE 3.8.11 or later. If your cluster uses MetalLB, upgrade to MKE 3.8.12 or later.

  2. Upgrade to MCR 25.0.12 or later.

  3. Upgrade to MKE 3.9.

If you are upgrading from MKE 3.7.x, the upgrade to MKE 3.8.x can restart your containers due to the container hash calculation change introduced in Kubernetes 1.31. To prevent containers from restarting simultaneously on all nodes, which the automated in-place cluster upgrade method can cause, use the phased in-place cluster upgrade method or the blue-green deployment upgrade method.

Release date

Name

Highlights

2026-OCT-05

MKE 3.9.7

  • Required images can be excluded from kubelet garbage collection

  • Prometheus metrics now scraped from CoreDNS.

  • Support for RHEL 9.8.

  • Support for Ubuntu 26.04.

  • Support for Windows Server 2025.

Important

If you previously disabled Ingress Controller to mitigate vulnerabilities, Mirantis recommends that following upgrade to MKE 3.9.0 you re-enable the component.

In addition, Mirantis recommends that you migrate from Ingress Controller to Envoy Gateway Controller.