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.

Prerequisites

Workload cluster along with management cluster and destination management clusters must be located at the same TCA-CP and be of the same version, v1.24.10+vmware.1 or v1.28.11+vmware.1. Management clsuter addon on source management cluster and destination management clusters must also be of the same version.

The Workload cluster's TBR should exist on destination management clusters.

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.

  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.
    Note: The management cluster will be grayed out if it does not meet the move prerequisite. Expand management cluster to view more details.
  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, 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 reflect 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. Check the events of the operation by expanding the workload cluster and navigating to the Events tab.

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

Example

Limitations
  • For Standard Cluster, 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.1 and TKG 2.5.2.
    • 1.27 managed by TKG 2.5.1 and TKG 2.5.2.
    • 1.28 managed by TKG 2.5.1 and TKG 2.5.2.
    • 1.29 managed by TKG 2.5.2.
    • 1.30 managed by TKG 2.5.2.
  • For Classy Standard Cluster, workload cluster version must be one of the following:
    • 1.27 managed by TKG 2.5.2.
    • 1.28 managed by TKG 2.5.2.
    • 1.29 managed by TKG 2.5.2
    • 1.30 managed by TKG 2.5.2
Note: The Classy Standard Cluster with IPAM will not move to destination management clusters.