Check whether traffic is routed to the Swarm cluster

  1. Check whether traffic is sent to the SLB instance attached to the Swarm cluster.

    Before you delete a Swarm cluster, check whether traffic is sent to the SLB instance attached to the Swarm cluster. Server Load Balancer provides the monitoring feature, which allows you to view traffic data by instance or listener.

    1. Log on to the Server Load Balancer console console. On the Server Load Balancers page, click the ID of the target SLB instance.
    2. On the Monitoring tab, a traffic monitoring chart is displayed.
  2. Check whether traffic is sent to the application deployed in the Swarm cluster.

    We recommend that you monitor the application deployed in the Swarm cluster for a period of time and make sure that no traffic is received before you delete the cluster. It may take a long time to upgrade client versions or update DNS cache, during which traffic may still be routed to the Swarm cluster.

Delete a Swarm cluster

After you make sure that the Kubernetes cluster is handling external requests normally and no traffic is received by the Swarm cluster, you can use the following steps to delete the Swarm cluster.

  1. Back up the configurations of the Swarm cluster.
    To ensure that you can quickly roll back to the Swarm cluster in case an unknown error occurs in the Kubernetes cluster, we recommend that you back up the configurations of the Swarm cluster. You should at least back up the following items:
    • Node labels, network settings, volume settings, ConfigMap settings, and SLB configurations.
    • Orchestration templates and log files.
  2. Release resources in the Swarm cluster.
    Notice When you delete a Swarm cluster, all resources that are attached to the cluster, such as ECS instances, applications, services, and SLB instances, will be released or deleted. Exercise caution when you perform this operation.

    Log on to the Container Service console. In the left-side navigation pane, choose Clusters > Clusters. Select the target cluster and click Delete in the Actions column to Delete clusters.

  3. Release disks.

    As introduced in Migrate cluster configurations, one disk can only be attached to one ECS instance. If a disk is used as a volume and needs to be migrated to the Kubernetes cluster, you must stop the ECS instance that uses the disk and migrate the instance to the Kubernetes cluster.

    If a disk is used for data storage and you do not need to migrate its data to the Kubernetes cluster, you can create a new disk in the Kubernetes cluster. After the Swarm cluster is deleted, the disk mounted to the cluster is not automatically released. The status of the disk is changed to Unattached.
    Note We recommend that you back up the data on disks before you release them.

    You can go to the ECS console to release disks that are mounted to the Swarm cluster.

    1. Log on to the Elastic Compute Service console. In the left-side navigation pane, choose Storage & Snapshots > Disks.
    2. On the Disks page, select the target disk and choose More > Release in the Actions column to release the disk.