3.8.6

Important

If you previously disabled Ingress Controller to mitigate vulnerabilities, Mirantis recommends that following upgrade to MKE 3.8.5 you re-enable the component. For detailed information on how to do this, refer to Configure NGINX Ingress Controller.

Release date	Name	Highlights
2025-JUNE-04	MKE 3.8.6	The MKE 3.8.6 patch release introduces the following product enhancement: Addition of CoreDNS memory resource settings. Ability to run CoreDNS on worker nodes. Updated Kubernetes to version 1.31.8.

Important

Upgrading to MKE 3.8.6 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.

• Enhancements
  • [MKE-12286] Addition of CoreDNS memory resource settings
  • [MKE-12181] Ability to run CoreDNS on worker nodes
  • [FIELD-7092] Kubernetes 1.31.8
• 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
• Major component versions
• Security information