When your application handles increasing traffic, a single server can become a bottleneck. By associating one or more Classic Load Balancer (CLB) or Network Load Balancer (NLB) instances with a cloud-native gateway, you distribute incoming requests across multiple backend servers to maintain application availability under high load.
This topic applies to cloud-native gateway Standard Edition instances only.
Prerequisites
Before you begin, make sure that:
A cloud-native gateway (Standard Edition) is deployed in Microservices Engine (MSE)
The CLB or NLB instance you plan to associate is not used by other products
No listeners on ports 80 or 443 exist on the CLB or NLB instance
Associate a load balancer instance
Log on to the MSE console.
In the left-side navigation pane, choose Cloud-native Gateway > Gateways. In the top navigation bar, select a region.
On the Gateways page, click the gateway ID.
On the Overview page, click the Endpoint tab. In the Gateway Ingress section, click Bind CLB in the upper-right corner.
In the Bind CLB/NLB panel, configure the following settings:
Parameter Description SLB Type Select CLB or NLB. Gateways associated with NLB instances support HTTP/3. Network Type Select Internet (public-facing) or VPC (internal). CLB Instance / NLB Instance Select the load balancer instance to associate with the gateway. ImportantDo not select a CLB instance that is already used by other products. Make sure that no listeners on ports 80 and 443 exist on the instance before you proceed. After the association, the forwarding protocol defaults to TCP/UDP. Do not change the protocol. Changing it may cause unexpected issues.
Click OK.
Verify the association
On the Gateway Ingress tab, click the refresh icon
in the upper-right corner.Confirm that the new load balancer instance appears in the list with an Association Status of Associated.
Gateway ingress parameters
After association, the Gateway Ingress section displays the following information for each load balancer instance:
| Parameter | Description |
|---|---|
| Instance ID | The ID of the SLB instance. Click the ID to view instance details. |
| Type | CLB or NLB. |
| Ingress IP Address | The IP address that receives traffic for the gateway. Resolve domain names to this address. |
| HTTP Port (vServer Group) | Port 80, opened on the cloud-native gateway. |
| HTTPS Port (vServer Group) | Port 443, opened on the cloud-native gateway. |
| Network Type | Internet or VPC. |
| Source | How the instance was created: Purchase (system-created) or Existing (user-created). |
| Association Status | Associated indicates the gateway is accessible through this instance. |
| Associated At | The date when the instance was associated with the gateway. |
Disassociate a load balancer instance
Before you disassociate an SLB instance, make sure that no traffic is routed to its IP address. If traffic is still active during disassociation, service disruptions may occur.
Log on to the MSE console.
In the left-side navigation pane, choose Cloud-native Gateway > Gateways. In the top navigation bar, select a region.
On the Gateways page, click the gateway ID.
On the Overview page, click the Endpoint tab. In the Gateway Ingress section, find the target SLB instance and click Disassociate in the Actions column.
In the dialog box that appears, click OK.
NoteFor system-created instances (Source: Purchase), choose whether to delete the SLB instance at the same time.
What happens after disassociation
Only the association between the gateway and the SLB instance is removed. The SLB instance itself is not deleted unless you chose to delete a system-created instance.
If you accidentally disassociate an instance, re-associate it by following the steps in Associate a load balancer instance.