All Products
Search

This Product

    Container Compute Service:Manage the ALB Ingress controller

    Document Center

    Container Compute Service:Manage the ALB Ingress controller

    Last Updated:Sep 12, 2025

    The Application Load Balancer (ALB) Ingress controller is a managed component for Container Compute Service (ACS) clusters that controls traffic forwarding based on the Layer 7 forwarding rules of ALB. This topic describes how to install, upgrade, and uninstall the ALB Ingress controller in an ACS cluster.

    Install the ALB Ingress controller

    Note

    For more information about the regions that support this component, see Regions and zones that support ALB.

    Installation during cluster creation

    1. Log on to the Container Compute Service console and click Create Cluster.

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

      Note

      For more information about other configurations, see Create an ACS cluster.

    Install the ALB Ingress controller in an existing cluster

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

    2. On the Clusters page, find the cluster that you want to manage and click its ID. In the left-side navigation pane of the cluster details page, choose Operations > Add-ons.

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

    4. In the Install ALB Ingress Controller dialog box, select New, Existing, or None for the Gateway Source as appropriate, and click OK.

      Instance source

      Description

      Result

      New (Recommended)

      • Network Type: You can create an ALB instance for Internet or Intranet as needed. For billing details, see Billing rules.

      • VPC: This value is the same as the VPC in which the cluster resides and cannot be modified.

      • vSwitch: The vSwitches corresponding to the zones supported by ALB under this VPC are displayed. You need to select two vSwitches in different zones. Otherwise, two available vSwitches will be automatically selected. You can also create a new vSwitch by clicking Create vSwitch.

      The controller will automatically create an AlbConfig named alb and the corresponding IngressClass resource. In AlbConfig, a listener with port 80 and HTTP is configured by default. For more information about listener extensions, see Create an HTTP listener.

      Existing (Recommended)

      You can select an existing ALB instance from the drop-down menu for reuse. Basic ALB instances are not supported. For more information, see Reuse an existing ALB instance.

      None (Optional)

      Only the ALB Ingress controller is installed. No ALB instance is created.

      Important

      The controller will not create the corresponding resources. You must manually create an AlbConfig and an IngressClass.

    What to do next

    After you install the ALB Ingress controller component, the cluster automatically creates an AlbConfig custom resource definition (CRD). You can then perform the following operations:

    • View the component YAML file: On the component card, click the image icon and select View In YAML to view the YAML file of the component's custom resource definition (CRD).

    • Enable component logs: On the component card, click the image icon, select Enable Log Collection, and then click Confirm. After the operation is complete, you can select View Logs or Disable Logging.

      Note

      To enable access logs for a specific ALB instance, navigate to Operations Management > Log Center > Network Component Logs in the navigation pane on the left of the ACS console. On the ALB Ingress page, click the Provisioning tab and enable access logs for the specified ALB instance.

    • Create custom resources: For more information about 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-side navigation pane, click Clusters.

    2. On the Clusters page, find the cluster that you want to manage and click its ID. In the left-side navigation pane of the cluster details page, choose Operations > Add-ons.

    3. On the Add-ons page, click the Networking tab. In the ALB Ingress Controller section, 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-side navigation pane, click Clusters.

    2. On the Clusters page, find the cluster that you want to manage and click its ID. In the left-side navigation pane of the cluster details page, choose Operations > Add-ons.

    3. On the Add-ons page, click the Networking tab. In the ALB Ingress Controller section, click Uninstall.

    4. In the Uninstall dialog box, click OK.

    Important

    Each AlbConfig custom resource corresponds to an ALB instance. If you no longer plan to use ALB Ingress, you must first delete the AlbConfig custom resources in the cluster. This automatically releases the corresponding ALB instances. After the instances are released, you can uninstall the ALB Ingress controller component. In the following scenarios, you must manually delete resources to avoid extra charges:

    • If you uninstall the ALB Ingress controller component, any remaining AlbConfig custom resources and their corresponding ALB instances are not released. You must manually delete these resources to avoid charges.

    • If you delete the AlbConfig custom resources after you uninstall the ALB Ingress controller component, the corresponding ALB instances are not released. You must manually delete the instances to avoid charges.

    References

    • For more information about the ALB Ingress controller component and its release notes, see ALB Ingress Controller.