VMware Telco Cloud Automation enables migration of a workload cluster from the existing management cluster to a new management cluster with the same version without any in-service impact on the workload cluster.

Procedure

  1. In the Cluster Instances tab of CaaS Infrastructure, click on the menu of the workload cluster and click Move to.
    The Move to tab is displayed.
    Note: The operation is only applicable for moving Standard Clusters and will be grayed out for Classy Standard Clusters and Classy Single Node Clusters.
  2. In the Move to page, a list of target management clusters will be displayed. Expand clusters in the list to view more details on cluster location and source.
  3. Select the cluster to be moved and click Next.
  4. Click Move. The status under Control Plane will move to Queued.
    Note: You will not be able to edit, delete, or upgrade, or perform nodepool operations like adding or deleting nodepool and addon during the Move to process.
  5. Check the status of the process under Control Plane. Once complete, the status will reflect as Provisioned. The target management cluster name will also be reflected under Management Cluster.

    You can also check the status of the operation by clicking on the workload cluster and navigating to Configuration and Control Plane.

    Note: If not pre-validated, the operation will fail and the status will reflect as Move Failed. In such a case, reinitiate the process.

    Limitations

    • Source management cluster and destination management clusters must be located at the same TCA CP.
    • Source management cluster and destination management clusters must be of same version, TKG 2.1.1 or TKG 2.5.1.
    • Management clsuter Addon on Source management cluster and destination management clusters must be of same version.
    • Type of TKG workload cluster must be Standard Cluster, Classy Standard Clusters and Classy Single Node Clusters will be grayed out.
    • The Workload cluster's TBR should exist on destination management clusters. Workload cluster version must be one of the following:
      • 1.24.10 managed by TKG 2.1.1
      • 1.26 managed by TKG 2.5.x
      • 1.27 managed by TKG 2.5.x
      • 1.28 managed by TKG 2.5.x.