Cloud-native Gateway usesAlibaba Cloud Server Load Balancer (SLB) to distribute requests and manage traffic. You can associate one or more Internet-facing or VPC-facing SLB instances with a gateway instance. When the traffic and load on your application increase, a single server might become overwhelmed. You can add an SLB instance to balance traffic and distribute the load across multiple servers, ensuring application availability.
This topic applies to Cloud-native Gateway Standard Edition.
Associate an SLB
-
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 ID of the gateway.
On the Overview page, click the Endpoint tab. In the upper-right corner of the Gateway Ingress section, 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 an SLB type. CLB and NLB are supported.
NoteGateways that use an NLB instance support the HTTP/3 protocol.
Network Type
Supported network types: Internet and VPC.
CLB Instance / NLB Instance
Select a CLB instance or an NLB instance.
ImportantDo not select a CLB instance already in use by another product. Before associating the instance, ensure no listeners are configured on ports 80 and 443.
Once associated, the forwarding protocol defaults to TCP/UDP. Do not change the protocol to avoid potential issues.
In the Gateway Ingress section, click
on the right to display the associated SLB instance.The following table describes the parameters in the list.
Parameter
Description
Instance ID
The ID of the SLB instance. Click the ID to view the instance details page.
Type
The type of the load balancer. Valid values: CLB and NLB.
Ingress IP Address
The IP address of the SLB instance, which serves as the ingress IP address for the gateway. You can configure domain name resolution for this IP address as needed.
HTTP Port (vServer Group)
Port 80 is enabled by default for the Cloud-native Gateway.
HTTPS Port (vServer Group)
Port 443 is enabled by default for the Cloud-native Gateway.
Network Type
The network type of the IP address for the SLB instance. Valid values: Internet and VPC.
Source
The source of the SLB instance.
If the system created the SLB instance, the value is Purchase.
If you added an existing SLB instance, the value is Existing.
Association Status
Indicates the association status of the SLB instance with the gateway. If the status is Associated, the gateway is accessible.
Associated At
Shows the time the SLB instance was associated with the gateway.
Disassociate an SLB
-
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 ID of the gateway.
In the navigation pane on the left, click Overview. Click the Endpoint tab. In the Gateway Ingress section, find the target SLB instance and click Disassociate in the Actions column.
In the confirmation dialog box that appears, click OK.
NoteBefore disassociating the instance, ensure that the ingress is not receiving traffic to avoid service disruptions.
This operation only removes the association, not the SLB instance itself. If you disassociate an instance by mistake, you can re-associate it to restore service.
When you disassociate an SLB instance whose Source is Purchase, you can choose whether to delete the SLB instance at the same time.
Related topics
To learn how to gradually migrate traffic from other gateways to an MSE Cloud-native Gateway, see Migrate traffic to a Cloud-native Gateway by using CLB.