3.9.0¶
Important
Due to REST API version changes, to upgrade to MKE 3.9 from MKE 3.8.10 or earlier, you must first upgrade to MKE 3.8.11. Following that, you must upgrade to MCR 25.0.12 or later. In addition, upgrading to MKE 3.8.x from MKE 3.7.x can cause your containers to restart, due to the hash calculation rule that was introduced in Kubernetes 1.31. As such, Mirantis recommends that you use the phased in-place cluster upgrade method or the blue-green deployment upgrade method to avoid the simultaneous containers restarts that the automated in-place cluster upgrade method can cause to occur in all nodes.
Release date |
Name |
Highlights |
|---|---|---|
2026-MAR-24 |
MKE 3.9.0 |
Initial MKE 3.9.0 release introducing the following key features and enhancements:
|
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.
- New features
- Enhancements
- Addressed issues
- Known issues
- [MKE-10152] Upgrading large Windows clusters can initiate a rollback
- [MKE-9699] Ingress Controller with external load balancer can enter crashloop
- [MKE-8914] Windows Server Core with Containers images incompatible with GCP
- [MKE-8814] Mismatched MTU values cause Swarm overlay network issues on GCP
- [MKE-12030] MKE telemetry setting overrides key/value in
daemon.json - [FIELD-8002] Flag conflict causes worker nodes not to upgrade
- Major component versions
- Security information