DocsICP FilingConsole
Documentation
Home Page Container Compute Service User Guide Network Ingress management ALB Ingress management Manage the ALB Ingress Controller add-on

Manage the ALB Ingress Controller add-on

Updated at:
Copy as MD
Product
My Favorites

Container Compute Service (ACS) provides a managed ALB Ingress Controller add-on that uses Layer 7 forwarding rules of Application Load Balancer (ALB). You can install, upgrade, and uninstall this add-on in ACS clusters.

Install the ALB Ingress Controller

Note

The ALB Ingress Controller supports only certain regions and zones.

During cluster creation

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

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

    Note

    Other cluster creation settings are described in 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 and 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 add-on, an AlbConfig custom resource is automatically created. You can:

  • View add-on YAML: On the add-on card, click the image icon and select View in YAML.

  • Enable add-on logging: On the add-on card, click the image icon, select Enable Component Logs, and click OK. You can then select View Component Logs or Disable Component Logs.

    Note

    To enable access logs for a specific ALB instance, in the left navigation pane of your cluster, choose Operations > Log Center > Network Component Logs > ALB Ingress. On the Data Import Management tab, enable access logs for the target ALB instance.

  • Create custom resources: Create AlbConfig and IngressClass resources by following 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. Find the ALB Ingress Controller add-on and click Upgrade.

  4. In the Upgrade 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. Find the ALB Ingress Controller add-on and click Uninstall.

  4. In the Uninstall dialog box, click OK.

Important

Each AlbConfig corresponds to one ALB instance. To stop using ALB Ingress, first delete the AlbConfig custom resources in the cluster, which automatically releases the corresponding ALB instances. Then uninstall the add-on. To avoid charges, manually delete resources in these scenarios:

  • If you uninstall the add-on before deleting the AlbConfig custom resources, the resources and their ALB instances remain and continue to incur charges. Delete them manually.

  • If you delete an AlbConfig after uninstalling the add-on, the corresponding ALB instance remains and continues to incur charges. Delete it manually.

Related documents

Previous：Limits on ALBNext：Methods to calculate ALB quotas