All Products
Search

This Product

    Container Compute Service:Manage the ALB Ingress Controller add-on

    Document Center

    Container Compute Service:Manage the ALB Ingress Controller add-on

    Last Updated:Jan 28, 2026

    Container Compute Service (ACS) provides a managed ALB Ingress Controller add-on that uses the Layer 7 forwarding rules of Application Load Balancer (ALB). This topic explains how to install, upgrade, and uninstall the ALB Ingress Controller in ACS clusters.

    Install the ALB Ingress Controller

    Note

    For a list of supported regions and zones, see Regions and zones supported by ALB.

    During cluster creation

    1. Log on to the ACS console and click Create Kubernetes Cluster.

    2. In the Component Configurations > Ingress section, select ALB Ingress.

      Note

      For other cluster creation settings, see Create an ACS cluster.

    On an existing cluster

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

    2. On the Clusters page, click the name of the target cluster. In the left navigation pane, click Add-ons.

    3. On the Add-ons page, click the Networking tab, find the ALB Ingress Controller add-on, then click Install.

    4. In the Install ALB Ingress Controller dialog box, for ALB Instance, select New, Existing, or None, configure other parameters, then click OK.

      Instance source

      Description

      Result

      (Recommended) New

      • Network Type: Create an Internet or Intranet ALB instance based on your requirements. For billing details, see ALB billing rules.

      • VPC: The default value is the same as the VPC of the cluster.

      • vSwitch: Displays the vSwitches that correspond to the zones supported by Application Load Balancer (ALB) in this virtual private cloud (VPC). You must specify two vSwitches in different zones. If you specify none, two available vSwitches are automatically selected. Alternatively, click Create vSwitch to create new vSwitches.

      The Controller automatically creates an AlbConfig named alb and a corresponding IngressClass resource. By default, the AlbConfig is configured with an HTTP listener on port 80. For more information about listener extensions, see Create an HTTPS listener.

      (Recommended) Existing

      Select an existing ALB instance from the drop-down list. Basic ALB instances are not supported. See Reuse an existing ALB instance.

      (Optional) None

      Installs only the ALB Ingress controller. No ALB instance is created.

      Important

      The controller does not create the related resources. You must manually create an AlbConfig and an IngressClass.

    Next steps

    After you install the ALB Ingress Controller add-on, the cluster automatically creates the AlbConfig Custom Resource Definition (CRD). Then perform the following operations:

    • View the add-on YAML: Click the image icon on the add-on card and select View in YAML.

    • Enable add-on logging: Click the image icon on the add-on card, select Enable Log Collection, and click OK. The View Logs and Disable Logging options become available under the image icon.

      Note

      To enable access logs for a specific ALB instance, in the left navigation pane of your ACS cluster go to Operations > Log Center > Network Component Logs > ALB Ingress. Then, click the Data Import Management tab to enable access logs for the specified ALB instance.

    • Create custom resources: For detailed steps on how to create AlbConfig and IngressClass custom resources, see Quick Start for ALB Ingresses.

    Upgrade the ALB Ingress Controller

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

    2. On the Clusters page, click the name of the target cluster. In the left navigation pane, click Add-ons.

    3. On the Add-ons page, click the Networking tab. On the ALB Ingress Controller add-on card, click Upgrade.

    4. In the Update dialog box, click OK.

    Uninstall the ALB Ingress controller

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

    2. On the Clusters page, click the name of the target cluster. In the left navigation pane, click Add-ons.

    3. On the Add-ons page, click the Networking tab. On the ALB Ingress Controller add-on card, click Uninstall.

    4. In the Uninstall dialog box, click OK.

    Important

    Each AlbConfig maps to one ALB instance. To remove ALB Ingress, first delete the AlbConfig resources to automatically release the ALBs, then uninstall the Controller add-on.

    To avoid unexpected charges, you must manually delete ALB instances if you:

    • Uninstall the Controller add-on before deleting AlbConfig resources.

    • Delete an AlbConfig resource after uninstalling the add-on.

    In both cases, the ALBs remain active and billable.

    References