MKE 3.5.11 known issues with available workaround solutions include:
[MKE-9358] cgroup v2 (unsupported) is enabled in RHEL 9.0 by default¶
As MKE does not support cgroup v2 on Linux platforms, RHEL 9.0 users will be unable to use the software due to cgroup v2 default enablement.
As a workaround, RHEL 9.0 users must disable cgroup v2.
[FIELD-5081] Node Feature Discovery Pods cause crash loop¶
Use of Node Feature Discovery (NFD) Pods can result in a crash loop in Linux systems that are running MCR 20.10.8 and earlier (moby/moby#42836).
As a workaround, update MCR to version 20.10.9 or later.
[MKE-8914] Windows Server Core with Containers images incompatible with GCP¶
The use of Windows ServerCore with Containers images will prevent kubelet from starting up, as these images are not compatible with GCP.
As a workaround, use Windows Server or Windows Server Core images.
[MKE-8814] Mismatched MTU values cause Swarm overlay network issues on GCP¶
Communication between GCP VPCs and Docker networks that use Swarm overlay networks will fail if their MTU values are not manually aligned. By default, the MTU value for GCP VPCs is 1460, while the default MTU value for Docker networks is 1500.
Select from the following options:
Create a new VPC and set the MTU value to 1500.
Set the MTU value of the existing VPC to 1500.
For more information, refer to the GCP official documentation: Change the MTU setting of a VPC network.