The VMware Telco Cloud Automation 3.2 introduces an improved appliance for managing your CaaS Infrastructure, Network Functions, and other features. Upgrading the existing 2.3 environment directly to 3.2 is not possible therefore, the migration is needed. The VMware Telco Cloud Automation 3.2 replaces the current VMware Telco Cloud Automation 2.x appliance.
Prerequisites
Ensure that you complete the following before upgrading to TCA 3.2:
TCA appliances are on VMware Telco Cloud Automation 2.3.x release.
Transform any v1 CaaS workload clusters to v2 CaaS workload clusters.
Update CaaS Management and Workload Clusters, node pools to Kubernetes version 1.24.10.
Delete all the management clusters in Not Active state, especially the ones failed in Deploy Cluster operation.
Proxy support has been discontinued from TCA 3.1.1. Delete the proxy configuration from Appliance management, if any.
Make a note of the inventory of all VIM, CaaS, NF catalog, NS instance to compare it after the migration is complete.
Delete Compute Clusters in the Infrastructure Automation as the functionality is deprecated and migration is not supported for Compute Clusters.
Take VM Snapshot of all the TCA appliances using the corresponding vCenter.
Take backups of each TCA appliance using the TCA Appliance Management portal.
For more information, see Backing Up and Restoring Kubernetes Clusters.