When you delete an Alibaba Cloud Service Mesh (ASM) gateway, the Server Load Balancer (SLB) instance configured for the ASM gateway is also deleted. This topic describes the cause of the issue and provides a solution.
Problem description
When you delete an ASM gateway, the SLB instance configured for the ASM gateway is also deleted.
Cause
When you create an ASM gateway, if you specify Create SLB Instance, an SLB instance is automatically created. In this case, when you delete the ASM
gateway, the SLB instance that is automatically created is also deleted.

Note If you specify Use Existing SLB Instance when you create an ASM gateway, the SLB instance that you use is retained after you
delete the ASM gateway.

Solution
To ensure that the SLB instance that is automatically created for an ASM gateway is retained when you delete the ASM gateway, perform the following steps:
- Obtain the IP address of the ASM gateway.
- Log on to the ASM console.
- In the left-side navigation pane, choose .
- On the Mesh Management page, find the ASM instance that you want to configure. Click the name of the ASM instance or click Manage in the Actions column.
- On the details page of the ASM instance, click ASM Gateways in the left-side navigation pane.
- On the ASM Gateways page, obtain the IP address of the ASM gateway whose SLB instance you want to retain
in the Kubernetes Service column.
- Obtain the ID of the SLB instance.
- Log on to the SLB console.
- In the left-side navigation pane, choose .
- On the Instances page, enter the ID of the ASM gateway obtained in Step 1 in the search box. In the search results, you can obtain the ID of the SLB instance.
- Modify the YAML file of the ASM gateway.
- Delete the ASM gateway and check whether the SLB instance that is automatically created
for the ASM gateway is also deleted.