Help Center> Ubiquitous Cloud Native Service> FAQs> Multi-Cloud Clusters> Multi-Cloud Cluster Resource Clearing Guide
Updated on 2023-04-12 GMT+08:00
View PDF

Multi-Cloud Cluster Resource Clearing Guide

If the multi-cloud cluster unregistration fails, you can try unregistration again. Before performing this operation, ensure that you have manually deleted the resources associated with the cluster on the AWS console. This section describes the names and quantities of these resources. You can access the EC2 panel and VPC panel of AWS to view and delete these resources.

In Table 1, ${clusterName} is your cluster name, and ${random5} is a random string of five characters.

Table 1 Names and quantities of resources

Console

Resource Type

Quantity

Name

EC2 panel

EC2

Master nodes: 3

Worker nodes: n

Master node: ${clusterName}-cp-${random5}

Worker node: ${clusterName}-md-${i}-${random5}. The default value of ${i} is 0.

Security group

5
  • ${clusterName}-node
  • ${clusterName}-lb
  • ${clusterName}-apiserver-lb
  • ${clusterName}-controlplane
  • default

The VPC corresponding to the preceding security groups is ${clusterName}-vpc.

EIP

3

${clusterName}-eip-apiserver

Volume

Nodes: 2

Determine the node to which the volume belongs based on the name of the EC2 instance to which the volume is mounted.

ELB

1

${clusterName}-apiserver. The corresponding VPC is ${clusterName}-vpc.

Network port

4

If Name is empty, the corresponding VPC is ${clusterName}-vpc.

VPC panel

VPC

1

${clusterName}-vpc

NAT

3
  • ${clusterName}-nat

    VPC: ${clusterName}-vpc; subnet: ${clusterName}-subnet-public-${az1}

  • ${clusterName}-nat

    VPC: ${clusterName}-vpc; subnet: ${clusterName}-subnet-public-${az2}

  • ${clusterName}-nat

    VPC: ${clusterName}-vpc; subnet: ${clusterName}-subnet-public-${az3}

Subnet

6
  • ${clusterName}-subnet-public-${az1}
  • ${clusterName}-subnet-private-${az1}
  • ${clusterName}-subnet-public-${az2}
  • ${clusterName}-subnet-private-${az2}
  • ${clusterName}-subnet-public-${az3}
  • ${clusterName}-subnet-private-${az3}

The VPC corresponding to the preceding subnets is ${clusterName}-vpc.

Route table

7
  • ${clusterName}-rt-public-${az1}. The explicit subnet association is ${clusterName}-subnet-public-${az1}.
  • ${clusterName}-rt-private-${az1}. The explicit subnet association is ${clusterName}-subnet-private-${az1}.
  • ${clusterName}-rt-public-${az2}. The explicit subnet association is ${clusterName}-subnet-public-${az2}.
  • ${clusterName}-rt-private-${az2}. The explicit subnet association is ${clusterName}-subnet-private-${az2}.
  • ${clusterName}-rt-public-${az3}. The explicit subnet association is ${clusterName}-subnet-public-${az3}.
  • ${clusterName}-rt-private-${az3}. The explicit subnet association is ${clusterName}-subnet-private-${az3}.
  • If Name is empty, the explicit subnet association is empty.

The VPC corresponding to the route tables is ${clusterName}-vpc.

Internet gateway

1

${clusterName}-igw The corresponding VPC is ${clusterName}-vpc.

Network ACL

1

If Name is empty and the associated object is 6 subnets, the corresponding VPC is ${clusterName}-vpc.
Parent topic: Multi-Cloud Clusters

Multi-Cloud Clusters FAQs

more