3.7.0¶
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.0, 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-AUG-31 |
MKE 3.7.0 |
Initial MKE 3.7.0 release introducing the following key features and enhancements:
|
- New features
- ZeroOps: certificate management
- ZeroOps: upgrade rollback
- ZeroOps: metrics
- Prometheus memory resources
- etcd event cleanup
- TLS passthrough
- TCP and UDP services
- Additional NGINX Ingress Controller options
- Setting for NGINX Ingress Controller default ports
- MetalLB
- Lameduck configuration options
- Multus CNI
- SAML proxy
- Addition of referral chasing LDAP parameter
- Enhancements
- 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-9358] cgroup v2 (unsupported) is enabled in RHEL 9.0 by default
- [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