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:Dec 11, 2024

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

    Install the ALB Ingress controller

    Note

    For more information about the regions that support the ALB Ingress controller, see Regions and zones in which ALB is available.

    Install the ALB Ingress controller when you create a cluster

    1. Log on to the ACS console. On the Clusters page, click Create Cluster.

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

      Note

      For more information about other parameter settings, 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, click the name of the cluster that you want to manage and choose Operations > Add-ons in the left-side navigation pane.

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

    4. In the Install ALB Ingress Controller dialog box, set Gateway Source to New, Existing, or None. The following table describes the three options.

      Important

      If you select New or Existing, an AlbConfig and IngressClass are automatically created after the ALB Ingress controller is installed. A listener that uses HTTP and listens on port 80 is configured in the AlbConfig.

      Comparison item

      New

      Existing

      None

      Use scenarios

      This is the first time you use ALB Ingresses in the cluster. No AlbConfig exists in the cluster.

      You want to use existing ALB instances.

      You want to configure an AlbConfig after the ALB Ingress controller is installed.

      How it works

      After an AlbConfig is created, an ALB instance is automatically created based on the AlbConfig.

      An AlbConfig is automatically created. The id field is set to the ID of the specified ALB instance.

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

      What to do next

      Set Network Type to the type of network used by the ALB instance and set vSwitch to the vSwitch of the ALB instance.

      Important

      To ensure high availability, we recommend that you select at least two vSwitches that reside in different zones.

      Set ALB Cloud-native Gateway to the ALB instance that you want to use. To use an AlbConfig to specify an ALB instance, see Reuse an existing ALB instance.

      Important

      Basic ALB instances are not supported.

      Select an existing AlbConfig or create an AlbConfig later.

    5. Click OK.

    What to do next

    After the ALB Ingress controller is installed, the cluster automatically creates an AlbConfig CRD. Then, you can perform the following operations:

    • View the YAML file of the component: Click the image icon on the component card and select View in YAML to view the YAML file of the AlbConfig CRD.

    • Enable log collection: Click the image icon on the component card and select Enable Log Collection. In the dialog box that appears, click OK. After the operation is complete, you can select View Logs or Disable Logging.

      Note

      Log on to the ACS cluster. In the left-side navigation pane, choose Operations > Log Center > Network Component Logs > ALB Ingress. On the page that appears, click the Data Import Management tab to enable access logs for the ALB instance.

    • Create custom resources: For more information about how to create an AlbConfig and IngressClass, see Get started with ALB Ingresses.

    Update the ALB Ingress controller

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

    2. On the Clusters page, click the name of the cluster that you want to manage and choose Operations > Add-ons in the left-side navigation pane.

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

    4. In the Upgrade Component message, click Confirm.

    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, click the name of the cluster that you want to manage and choose Operations > Add-ons in the left-side navigation pane.

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

    4. In the Uninstall message, click OK.

    Important

    Each AlbConfig corresponds to an ALB instance. If you no longer need the ALB Ingress controller, delete all AlbConfigs in the cluster, and the corresponding ALB instances will be released. Then, you can uninstall the ALB Ingress controller. In the following scenarios, you must manually delete AlbConfigs to avoid additional fees:

    • After you uninstall the ALB Ingress controller, AlbConfigs and the corresponding ALB instances in the cluster are not released. They continue to incur fees. You must manually delete the AlbConfigs and the corresponding ALB instances.

    • After you uninstall the ALB Ingress controller and delete AlbConfigs in the cluster, the corresponding ALB instances in the cluster are not released. They continue to incur fees. You must manually delete the ALB instances.

    References