Release Notes

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.

MKE 3.8.14 current

The MKE 3.8.14 patch release focuses exclusively on bug fixes.

3.8.14
MKE 3.8.13

Patch release for MKE 3.8 introducing the following key features:

  • Configurable etcd request quota via cluster_config.etcd_request_quota

  • Configurable Kubernetes secrets encryption at rest in etcd

3.8.13
MKE 3.8.12

The MKE 3.8.12 hotfix release resolves the missing CustomResourceDefinition (CRD) for MetalLB issue that was identified in the 3.8.11 release.

3.8.12
MKE 3.8.11

Patch release for MKE 3.8 introducing the following key feature:

  • Upgrade of Docker form version 24.0.9 to version 25, for the purpose of supporting MCR 23.x, MCR 25.x, and MCR 29.x.

3.8.11
MKE 3.8.10

Patch release for MKE 3.8 introducing the following key feature:

  • Removal of weak CBC-mode ciphers

3.8.10
MKE 3.8.9

The MKE 3.8.9 patch release focuses exclusively on bug fixes and CVE mitigation.

3.8.9
MKE 3.8.8

Patch release for MKE 3.8 introducing the following key features:

  • Ability to set explicit user Id for each node-feature-discovery container

  • Addition of targeted LDAP synchronization functionality

3.8.8
MKE 3.8.7

Patch release for MKE 3.8 introducing the following key features:

  • Addition of kubelet image pull configuration settings

  • Addition of configMap persist node local DNS configuration setting

  • Updated Enzi to version 1.3.1.

  • Updated Kubernetes to version 1.31.10.

3.8.7
MKE 3.8.6

Patch release for MKE 3.8 introducing the following key features:

  • Addition of CoreDNS memory resource settings.

  • Ability to run CoreDNS on worker nodes.

  • Updated Kubernetes to version 1.31.8.

3.8.6
MKE 3.8.5

Patch release for MKE 3.8 introducing the following key features:

  • Addition of CoreDNS ConfigMap persist configuration setting.

  • Ability to disable/re-enable client bundle generation and use.

  • Updated Kubernetes to version 1.31.8.

3.8.5
MKE 3.8.4

Patch release for MKE 3.8 that focuses exclusively on CVE mitigation. For detail on the specific CVEs addressed, refer to Security information.

3.8.4
MKE 3.8.3

The MKE 3.8.3 patch release introduces the following product enhancement:

  • Updated Kubernetes to version 1.31.5.

3.8.3
MKE 3.8.2

Patch release for MKE 3.8 that focuses exclusively on bug fixes and CVE mitigation.

3.8.2
MKE 3.8.1

Patch release for MKE 3.8 that focuses exclusively on CVE mitigation.

3.8.1
MKE 3.8.0

Initial MKE 3.8.0 release introducing the following key features:

  • Updated Kubernetes to version 1.31.1.

  • Added the ingress_extra_args.default_backend_service MKE configuration setting for NGINX Ingress Controller.

3.8.0