3.8.0¶
Release date |
Name |
Highlights |
---|---|---|
2024-DEC-04 |
MKE 3.8.0 |
Initial MKE 3.8.0 release introducing the following key features and enhancements:
|
Important
Upgrading to MKE 3.8.0 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.
- New features
- Enhancements
- Addressed issues
- Known issues
- [FIELD-7023] Air-gapped swarm-only upgrades fail if images are inaccessible
- [MKE-11535] ucp-nvidia-gpu-feature-discovery pods may enter CrashLoopBackOff state
- [MKE-11531] NodeLocal DNS Pods attempt to deploy to Windows nodes
- [MKE-11525] Kubelet node profiles fail to supersede global setting
- [MKE-10152] Upgrading large Windows clusters can initiate a rollback
- [MKE-9699] Ingress Controller with external load balancer can enter crashloop
- [MKE-8662] Swarm only manager nodes are labeled as mixed mode
- [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-7469]
storage_expt_enabled set
totrue
prevents kubelet start up
- Major component versions
- Security information