Grant MSE Ingress controller access permissions

Updated at:
Copy as MD

To access services through MSE Ingress in an ACK Serverless cluster, you must grant the MSE Ingress controller the relevant access permissions for MSE before you deploy the services. This topic describes how to grant permissions to the MSE Ingress controller in an ACK Serverless cluster.

Step 1: Install the MSE Ingress controller

Method 1: Install during cluster creation

When you create an ACK Serverless cluster, go to the Component Configurations step. In the Ingress section, select MSE Ingress. For more information about how to create an ACK Serverless cluster, see Create an ACK Serverless cluster.

Method 2: Install on an existing cluster

  1. Log on to the ACK console. In the left navigation pane, click Clusters.

  2. On the Cluster List page, click the name of the destination cluster or click Details in the Actions column.

  3. In the left navigation pane of the cluster management page, choose O&M Management > Component Management.

  4. On the Add-ons page, click the Network tab. In the lower-right corner of the MSE Ingress controller add-on, click Install.

  5. In the dialog box that appears, click OK.

Step 2: Authorize the MSE Ingress controller

  1. Go to the Cloud Resource Access Authorization page and click Confirm.

    Successful authorization grants the MSE Ingress controller the AliyunMSEForECIRole role.

  2. Log on to the ACK console. In the left navigation pane, click Clusters.

  3. On the Clusters page, click the name of your cluster. In the left navigation pane, click Workloads > Deployments.

  4. At the top of the Deployments page, select All Namespaces from the drop-down list. In the search box, enter ack-mse-ingress-controller to find the ack-mse-ingress-controller application. In the Actions column, choose More > Redeploy, and then click OK.

    After the redeployment is complete, click the ack-mse-ingress-controller application on the Deployments page. On the Pods tab, verify that the Pod is in the Running state, which indicates a successful redeployment.