Cloud-native gateways use Alibaba Cloud Server Load Balancer (SLB) instances as Ingresses to distribute and manage requests. You can associate one or more Internet-facing or internal-facing SLB instances with a cloud-native gateway. When the requests and load of an application increase, a single server may be overwhelmed by the requests. You can associate SLB instances with a cloud-native gateway to distribute requests to multiple servers to ensure the availability of the application.
Associate an SLB instance with a gateway
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 name of the gateway.
On the Gateway Ingress tab of the Overview page, click Bind CLB/NLB.
In the Bind CLB/NLB panel, configure the parameters and click OK.
The following table describes the parameters.
Parameter
Description
SLB Type
Select CLB or NLB.
NoteGateways that are associated with Network Load Balancer (NLB) instances support HTTP/3.
Network Type
Select the network type based on the IP address of the SLB instance. Valid values: Internet and VPC.
SLB Instance
Select the SLB instance that you want to associate with the gateway from the drop-down list.
ImportantDo not select an SLB instance that is used by other services. You must make sure that the SLB instance that you select does not listen on ports 80 and 443.
Click
in the upper-right corner of the Gateway Ingress tab. If the association is successful, the associated SLB instance appears. The following table describes the parameters on the Gateway Ingress tab.
Parameter
Description
Instance ID
The ID of the SLB instance. You can click the ID to view detailed information about the SLB instance.
Type
Valid values: CLB and NLB.
Ingress IP Address
The IP address of the SLB instance that is used to access the gateway. You can resolve domain names to this IP address.
HTTP Port (vServer Group)
Port 80 is opened on cloud-native gateways.
HTTPS Port (vServer Group)
Port 443 is opened on cloud-native gateways.
Network Type
The type of the SLB instance. Valid values: Internet and VPC.
Source
Specifies how the SLB instance is created.
If the current SLB instance is created by the system, the column displays Purchase.
If the current SLB instance is created by you, the column displays Existing.
Association Status
The status of the association between the SLB instance and gateway. If the column displays Associated, the gateway is accessible.
Associated At
The date on which the SLB instance is associated with the gateway.
Disassociate an SLB instance from a cloud-native gateway
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 name of the gateway.
On the Gateway Ingress tab of the Overview page, find the gateway and click Disassociate in the Actions column.
In the message that appears, click OK.
NoteBefore you disassociate an SLB instance, you must make sure that no requests are sent to the IP address of the SLB instance. Otherwise, business disruptions may occur.
The disassociation operation deletes only the association between a cloud-native gateway and an SLB instance. If you accidentally disassociate an SLB instance from a cloud-native gateway, you can associate the SLB instance with the gateway again.
When you disassociate an SLB instance that is created by the system, you can specify whether to delete the SLB instance at the same time.
References
For information about how to migrate traffic from other gateways to MSE cloud-native gateways, see CLB-based migration.