Mis-deletion Handling for Cluster ULB

1. Pre-operations

Load balance (ULB) is divided into internal and external networks. In case of deletion by mistake, first, it is necessary to rebuild the ULB and ensure that the original ULB IP address remains unchanged.

• For internal ULB, you need to contact technical support for non-standard creation of ULB with a designated internal IP;
• For public ULB, you need to create a ULB with a designated EIP (provided that the original EIP is not applied by other customers), and bind this EIP when creating the public ULB.

2. Mistaken Deletion of Master ULB

Master ULB, i.e., the ULB bound to the cluster APIServer, is used to access the APIServer on the three Master nodes. The internal Master ULB is automatically generated when the cluster is created; if the external network APIServer is activated at the same time, the external Master ULB is also generated.

The naming rule is uk8s-xxxxxxxx-master-ulb4(internal ULB)/uk8s-xxxxxxxx-master-ulb4-external(public ULB).

The recovery steps are as follows:

1. When creating a ULB, the type needs to be specified as packet forwarding;
2. Create a new VServer with port 6443 and specify the type as TCP;
3. Add three Master nodes as service nodes.

3. Mistake in Deleting Cluster Service ULB

1. When creating ULB, the type of ULB should match the type of Service; when the service type is TCP/UDP, specify packet forwarding, and when it is HTTP/HTTPS, specify request proxy type;
2. Delete the original Service within the cluster;
3. According to the documentation, rebind the ULB and Service: Create Service Using Existing ULB.