The Microservices Engine (MSE) Ingress Controller component is available on the Add-ons page in the Container Service for Kubernetes (ACK) console to better serve customers who use ACK. The MSE Ingress Controller component on the Marketplace page will reach end of life (EOL) and is discontinued. We recommend that you migrate the MSE Ingress Controller component to the Add-ons page at the earliest opportunity. This topic describes how to migrate the MSE Ingress Controller component from the Marketplace page to the Add-ons page in the ACK console.
Migration description
You can follow instructions in this topic to migrate the MSE Ingress Controller component if you have installed the component for your cluster on the Marketplace page.
The MSE Ingress Controller component is not a network data plane, but is a control plane that is used to manage MSE cloud-native gateways and configurations. The MSE Ingress Controller component does not handle any service requests. The MSE Ingress Controller component works as a traffic bypass to manage MSE cloud-native gateways that handle service requests. When you migrate the MSE Ingress Controller component, business continuity is not adversely affected.
During the migration, operations are performed only on the MSE Ingress Controller component. Do not delete MseIngressConfig CustomResourceDefinition (CRD) configurations in your cluster. An MseIngressConfig CRD has a one-to-one mapping with an MSE cloud-native gateway. If you delete an MseIngressConfig CRD, the associated MSE cloud-native gateway is deleted.
Procedure
Step 1: Uninstall the ack-mse-ingress-controller component on the Marketplace page
Log on to the managed ACK console, ACK Serverless console, or ACS console.
In the left-side navigation pane, click Clusters. Then, click the name of the cluster that you want to manage.
In the left-side navigation pane, choose .
On the Helm page, find the ack-mse-ingress-controller component, and click Delete in the Actions column.
In the Delete dialog box, click OK.
The ack-mse-ingress-controller component is uninstalled.
Step 2: Install the MSE Ingress Controller component on the Add-ons page
Log on to the managed ACK console, ACK Serverless console, or ACS console.
In the left-side navigation pane, click Clusters. Then, click the name of the cluster that you want to manage.
In the left-side navigation pane, choose .
On the Add-ons page, click the Networking tab. In the lower-right corner of the MSE Ingress Controller component card, click Install.
In the Install MSE Ingress Controller dialog box, click OK.
MseIngressConfig CRDs and MSE cloud-native gateways have one-to-one mappings. If you select Cascade Delete SLB Instance, the purchased SLB instance is deleted when you delete an MseIngressConfig CRD.
If the mse-ingress-controller component is displayed in the component list in the ACK console, the component is successfully installed.