The ALB Ingress controller is a fully managed add-on that routes Layer 7 traffic to your ACK cluster using forwarding rules defined on Application Load Balancer (ALB). This topic explains how to install, upgrade, and uninstall the ALB Ingress controller in an ACK managed cluster or dedicated cluster.
For supported regions, see Regions and zones that support ALB.
Install the ALB Ingress controller
Choose one of the following paths based on your situation:
Creating a new cluster: Configure the controller as part of cluster creation.
Using an existing cluster: Install the controller from the Add-ons page after the cluster is running.
Install during cluster creation
When creating an ACK managed cluster or dedicated cluster, go to the Ingress section and select ALB Ingress.
Set ALB Instance to New, Existing, or None:
| Instance source | Description | What gets created |
|---|---|---|
| (Recommended) New | Create an ALB instance. Configure the following: <br>- Network Type: Internet or Intranet <br>- VPC: defaults to the cluster VPC <br>- vSwitch: specify two vSwitches in different zones; if left blank, two available vSwitches are selected automatically. To create new vSwitches, click Create vSwitch. <br>For billing details, see ALB billing rules. | An AlbConfig named alb and a corresponding IngressClass resource. The AlbConfig is configured with an HTTP listener on port 80 by default. To add an HTTPS listener, 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. | An AlbConfig named alb and a corresponding IngressClass resource, bound to the selected ALB instance. |
| (Optional) None | Install the controller only, without creating an ALB instance. Use this option when you plan to specify ALB instances directly in your Ingress YAML. | No ALB instance or related resources are created. You must manually create an AlbConfig and IngressClass. |
Install on an existing cluster
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click Add-ons.
On the Add-ons page, click the Networking tab. In the Networking section, click Install on the ALB Ingress Controller card.
In the Install ALB Ingress Controller dialog box, select New, Existing, or None for ALB Instance, configure the remaining parameters, and click OK. Refer to the table in the previous section for the available options and their results.
Upgrade the ALB Ingress controller
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click Add-ons.
On the Add-ons page, click the Networking tab. In the ALB Ingress Controller section, click Upgrade.
NoteIf no Upgrade button is displayed, the controller is already at the latest version.
In the Update dialog box, click OK.
Uninstall the ALB Ingress controller
Delete the AlbConfig from your cluster before uninstalling the controller.
The ALB instance is not released and continues to incur fees.
Any subsequent attempt to delete the AlbConfig fails because the controller is no longer present to complete the deletion. To recover, reinstall the controller, delete the AlbConfig to release the ALB instance, and then uninstall the controller again.
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click Add-ons.
On the Add-ons page, click the Networking tab. In the ALB Ingress Controller section, click Uninstall.
In the Uninstall dialog box, click OK.
What's next
To learn about controller features and version history, see Release notes of ALB Ingress Controller.
To start routing traffic with ALB Ingress rules, see Create an ALB Ingress.
If you are using an ACK dedicated cluster, also grant the required access permissions to the ALB Ingress controller. See Grant access permissions to the ALB Ingress controller for an ACK dedicated cluster.