The Application Load Balancer (ALB) Ingress controller is a fully managed component that controls the traffic forwarding of Container Service for Kubernetes (ACK) 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 ACK managed cluster or ACK dedicated cluster.
Install the ALB Ingress controller
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
When you create an ACK managed cluster or ACK dedicated cluster, select ALB Ingress in the Ingress section.
You can set Gateway Source to New, Existing, or None. The following table describes the three options.
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 | 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. |
Install the ALB Ingress controller in an existing cluster
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose .
On the Add-ons page, click the Networking tab. In the Networking section, find the ALB Ingress Controller card and click Install in the lower-right corner.
In the Install ALB Ingress Controller dialog box, set Gateway Source to New, Existing, or None. The following table describes the three options.
ImportantIf you select New or Existing, an AlbConfig and IngressClass are automatically created after the ALB Ingress controller is installed. A
listenerthat 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
idfield 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.
ImportantTo 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.
ImportantBasic ALB instances are not supported.
Select an existing AlbConfig or create an AlbConfig later.
Click OK.
Update the ALB Ingress controller
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose .
On the Add-ons page, click the Networking tab, find ALB Ingress Controller, and then click Upgrade.
NoteIf the Upgrade button is not displayed for ALB Ingress Controller, the ALB Ingress controller in your cluster is already updated to the latest version.
In the Upgrade message, click OK.
Uninstall the ALB Ingress controller
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose .
On the Add-ons page, click the Networking tab, find ALB Ingress Controller, and then click Uninstall.
In the Uninstall message, click OK.
Each AlbConfig corresponds to an ALB instance. When you uninstall the ALB Ingress controller, AlbConfigs and the corresponding ALB instances in the cluster are not released. They continue to incur fees. After the ALB Ingress controller is uninstalled, if you delete the AlbConfigs, the corresponding ALB instances are not released.
If you no longer need the ALB Ingress controller, delete all AlbConfigs in the cluster before uninstalling the ALB Ingress controller.
References
If your cluster is an ACK dedicated cluster, you need to grant the cluster permissions to access the ALB Ingress controller. For more information, see Authorize an ACK dedicated cluster to access the ALB Ingress controller.
For more information about how to use ALB Ingresses, see Get started with ALB Ingresses.