Release Notes
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.
The MKE 3.9.4 patch release focuses exclusively on bug fixes.
The MKE 3.9.3 patch release introduces the following key features:
Configurable etcd request quota via
cluster_config.etcd_request_quotaConfigurable Kubernetes secrets encryption at rest in etcd
Kubernetes Descheduler support
Kubernetes Metrics Server support
The MKE 3.9.2 hotfix release resolves the missing CustomResourceDefinition (CRD) for MetalLB issue that was identified in the 3.9.1 release.
The MKE 3.9.1 hotfix release resolves the Interactive Container Exec failure issue identified in the initial 3.9.0 release.
Initial MKE 3.9.0 release introducing the following key features and enhancements:
Introduction of Envoy Gateway Controller 1.7
Introduction of client bundle expiration
Component upgrades:
Kubernetes 1.34.3
Calico 3.31.2
Prometheus 3.5.0
Docker CLI 29.0.4
Docker Client 0.2.1
Docker REST API 1.52.0
Golang 1.25.7
Note
MKE 3.9.0 is Kubernetes CNCF certified. You can review the conformance test results at https://github.com/cncf/k8s-conformance/pull/4097.
Considerations
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.
Upgrading from one MKE minor version to another minor version can result in the downgrading of MKE middleware components. For more information, refer to the middleware versioning tables in the release notes of both the source and target MKE versions.