Skip to content

Known issues#

MKE 3.9.6 known issues with available workaround solutions include:

[MKE-10152] Upgrading large Windows clusters can initiate a rollback#

Upgrades can rollback on a cluster with a large number of Windows worker nodes.

Workaround:

Invoke the --manual-worker-upgrade option and then manually upgrade the workers.

[MKE-9699] Ingress Controller with external load balancer can enter crashloop#

Due to the upstream Kubernetes issue 73140, rapid toggling of the Ingress Controller with an external load balancer in use can cause the resource to become stuck in a crashloop.

Workaround:

  1. Log in to the MKE web UI as an administrator.

  2. In the left-side navigation panel, navigate to > Admin Settings > Ingress.

  3. Click the Kubernetes tab to display the HTTP Ingress Controller for Kubernetes pane.

  4. Toggle the HTTP Ingress Controller for Kubernetes enabled control to the left to disable the Ingress Controller.

  5. Use the CLI to delete the Ingress Controller resources:

    kubectl delete service ingress-nginx-controller-admission --namespace ingress-nginx
kubectl delete deployment ingress-nginx-controller --namespace
ingress-nginx

  6. Verify the successful deletion of the resources:

    kubectl get all --namespace ingress-nginx

    Example output:

    No resources found in ingress-nginx namespace.

  7. Return to the HTTP Ingress Controller for Kubernetes pane in the MKE web UI and change the nodeport numbers for HTTP Port, HTTPS Port and TCP Port.

  8. Toggle the HTTP Ingress Controller for Kubernetes enabled control to the right to re-enable the Ingress Controller.

[MKE-12030] MKE telemetry setting overrides key/value in daemon.json file#

MKE removes the telemetry key/value from the MCR 25 daemon.json file configuration.

Workaround:

Disable the telemetry function.

  • Users running MKE 3.x in addition to MCR 25.0.13 or lower:

    1. Verify that you have a valid license affixed to MKE.

    2. Log in to the MKE web UI as an administrator.

    3. In the left-side navigation panel, navigate to > Admin > Config.

    4. Disable both options under Usage Reporting and click Save.

    5. Verify the presence of "telemetry": false in the /etc/docker/daemon.json file.

    6. Run sudo systemctl reload docker.service on all manager nodes.

  • All other users must directly edit the daemon.json file to include "telemetry": false.

[FIELD-8002] Flag conflict causes worker nodes not to upgrade#

Worker nodes fail to complete upgrade when the --manual-worker-upgrade flag is used in combination with custom registries.

Workaround:

Before you perform a manual worker upgrade, you must either pull the newest images and retag them to match custom-registry style, or use the images --all-nodes flag, as exemplified below:

docker run --rm --security-opt label=disable -v
/var/run/docker.sock:/var/run/docker.sock
private_registry/namespace/ucp:<mke-version>  images --all-nodes