3.7.1¶
Caution
Upstream Kubernetes has removed the in-tree AWS cloud provider. Kubernetes 1.27.4, which is the version that is configured to MKE 3.7.0, does not support the AWS in-tree cloud provider. As such, if your MKE cluster is using the AWS in-tree cloud provider, you must upgrade to MKE 3.7.12 or later, as these versions support a transition pathway to an alternative external AWS cloud provider.
If you attempt to upgrade a cluster that uses AWS in-tree cloud provider to MKE 3.7.1, the upgrade will fail and you will receive the following error message:
Your MKE cluster is currently using the AWS in-tree cloud provider, which
Kubernetes no longer supports. Please defer upgrading to MKE 3.7 until a
version that supports migration to an alternative external AWS cloud
provider is released.
Release date |
Name |
Highlights |
---|---|---|
2023-SEPT-26 |
MKE 3.7.1 |
Patch release for MKE 3.7 introducing the following enhancements:
|
- Enhancements
- [MKE-10118] Support bundle metrics additions for new MKE 3.7 features
- [MKE-10106] Added ability to filter organizations by name in MKE web UI
- [MKE-10069] Increased Docker and Kubernetes CIS benchmark compliance
- [MKE-10045] MetalLB supports MKE-specific loglevel
- [MKE-10041] Improved Kubernetes role creation error handling in MKE web UI
- [MKE-10020] Increased SAML proxy feedback detail
- [MKE-9994] Upgrade verifies that cluster nodes have minimum required MCR
- [MKE-9991] kube-proxy now binds only to localhost
- [MKE-9653] Enablement of read-only rootfs for specific containers
- [MKE-9362] Support for cgroup v2
- [MKE-9105] Added MKE web UI capability to add OS constraints to swarm services
- [FIELD-6026] Added ability to set support bundle collection windows
- [FIELD-6024] Added ability to set line limit of log files in support bundles
- [FIELD-5936] Addition of search function to Grants > Swarm in MKE web UI
- 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
- [FIELD-6785] Reinstallation can fail following cluster CA rotation
- [FIELD-6402] Default metric collection memory settings may be insufficient
- Major component versions
- Security information
- Deprecations