Skip to content

Upgrade NGINX ingress controller#

If in your MKE 3 cluster you deployed the Helm-based patched ingress controller featured in How to Mitigate Risk for NGINX Ingress Controller Vulnerabilities Affecting Mirantis Kubernetes Engine, you must revert back to the embedded version of ingress-nxinx before you upgrade your MKE 3 cluster to MKE 4. The instructions herein will help you to you verify, uninstall, and re-enable the default NGINX Ingress Controller in your MKE 3 cluster.

  1. Download and configure the MKE Client Bundle.

  2. Run the kubectl get ingressclass -o wide command to verify whether an ingress controller is running on your MKE 3 cluster. Your next action depends on the output you receive.

    Output Action to take
    No resources found Enable the Nginx ingress controller
    NAME is nginx-default Verify the configuration
    NAME is not nginx-default Uninstall the patched controller

  3. If verification returns No resources found, proceed to step 4 to enable the embedded Nginx ingress controller. If it returns nginx-default, skip to step 5 to verify the configuration. Otherwise, uninstall the patched ingress controller:

    • Uninstall using Helm:

      helm uninstall ingress-nginx -n ingress-nginx

    • Uninstall using kubectl (offline mode):

      kubectl delete ingressclass nginx --ignore-not-found

  4. Enable the Nginx ingress controller:

  5. Verify the ingress configuration:

    1. Download and configure the MKE Client Bundle.

    2. Obtain the MKE configuration file.

    3. Ensure that the cluster_config.ingress_controller.enabled configuration parameter in the MKE configuration file is set to true.