Manage the ALB Ingress controller

更新时间:
复制 MD 格式

ACK Serverless clusters provide a managed ALB Ingress controller that uses the Layer 7 forwarding rules of Application Load Balancer (ALB). This topic describes how to install, upgrade, and uninstall the ALB Ingress controller in an ACK Serverless cluster.

Install the ALB Ingress controller

Note

For supported regions, see Regions and zones that support ALB.

During cluster creation

When you create an ACK Serverless cluster, on the Component Configurations page, select ALB Ingress in the Ingress section. Then, under ALB Instance, select Create or None based on your requirements.

Gateway source

Description

Result

New

Installs the ALB Ingress controller and creates an associated ALB instance.

You can create an Intranet or Intranet ALB instance based on your requirements. For billing details, see ALB billing rules.

The controller automatically creates an AlbConfig object named alb and the corresponding IngressClass resource. The AlbConfig object defines a default listener that uses HTTP on port 80. To learn how to add more listeners, see Create an HTTPS listener.

None

Installs only the ALB Ingress controller without creating an ALB instance.

Important

The controller does not create these resources. You must manually create an AlbConfig object and an IngressClass resource.

For an existing cluster

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

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

  3. On the Add-ons page, click the Network tab. In the Networking component area, click Install in the bottom-right corner of the ALB Ingress Controller component card.

  4. In the Install - ALB Ingress controller dialog box, under Gateway Source, select Create, Select Existing VPC , or None based on your requirements, and then click OK.

    Instance source

    Description

    Result

    (Recommended) New

    • Network Type: Create an Internet or Private Network ALB instance, depending on your needs. For billing details, see ALB billing rules.

    • VPC: The default value is the Virtual Private Cloud (VPC) in which the cluster is deployed.

    • vSwitch: The console displays the vSwitches in the availability zones that are supported by ALB within this VPC. You must select two vSwitches that reside in different availability zones. If you do not specify vSwitches, the system automatically selects two available vSwitches. You can also click Create vSwitch to create new vSwitches.

    The controller automatically creates an AlbConfig object named alb and the corresponding IngressClass resource. The AlbConfig object defines a default listener that uses HTTP on port 80. To learn how to add more listeners, see Create an HTTPS listener.

    (Recommended) Existing

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

    (Optional) None

    Installs only the ALB Ingress controller without creating an ALB instance.

    Important

    The controller does not create these resources. You must manually create an AlbConfig object and an IngressClass resource.

Upgrade the ALB Ingress controller

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

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

  3. On the Add-ons page, click the Network tab. Find the ALB Ingress controller card and click Upgrade.

    Note

    If the Upgrade button is not visible on the ALB Ingress controller card, the component is up to date.

  4. In the Update dialog box, click OK.

Uninstall the ALB Ingress controller

Important
  • Before uninstalling the component, you must delete all AlbConfig objects in the cluster. The ALB Ingress controller then automatically releases the associated ALB instances.

  • After you uninstall the ALB Ingress controller:

    • If any AlbConfig objects still exist in the cluster, the associated ALB instances are not released and billing continues.

    • If you manually delete an AlbConfig object after the controller is uninstalled, the associated ALB instance cannot be released because the reconciliation process cannot be completed without the controller. We recommend that you reinstall the controller, delete the AlbConfig object to ensure the controller releases the associated ALB instance, and then uninstall the controller.

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

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

  3. On the Add-ons page, click the Network tab. Find the ALB Ingress controller card and click Uninstall.

  4. In the Uninstall dialog box, click OK.