3.7.11¶
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.11, 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 |
---|---|---|
2024-JULY-8 |
MKE 3.7.11 |
Patch release for MKE 3.7 that focuses exclusively on CVE mitigation. For detail on the specific CVEs addressed, refer to Security information. |
- Enhancements
- Addressed issues
- Known issues
- [MKE-11535][FIELD-7110] 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
- [FIELD-7023] Air-gapped upgrades fail if images are inaccessible
- [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
- Major component versions
- Security information
- Deprecations