You can upgrade the existing Management Cluster to the latest versions supported in VMware Telco Cloud Automation.
| Current TKG/Management Cluster Version | Target TKG/Management Cluster Version | Notes |
|---|---|---|
| TKG 2.1.1/v1.24.10+vmware.1 | TKG 2.2.0/v1.25.7+vmware.2 | If the management cluster is migrated from VMware Telco Cloud Automation v2.3, upgrade management cluster addon first before upgrading to the next kubernetes version. |
| TKG 2.2.0/v1.25.7+vmware.2 | TKG 2.3.1/v1.26.8+vmware.1 | |
| TKG 2.3.1/v1.26.8+vmware.1 | TKG 2.4.1/v1.27.5+vmware.1 | Upgrade all workload clusters to v1.26.8+vmware.1 before upgrading the management cluster. |
| TKG 2.4.1/v1.27.5+vmware.1 | TKG 2.5.1/v1.28.7+vmware.1 |
|
TKG 2.5.0/v1.28.4+vmware.1 |
TKG 2.5.1/v1.28.7+vmware.1 |
Before upgrading Kubernetes to the latest version, consider the following constraints and prepare for the upgrade plan:
VMware Telco Cloud Automation preserves the customization performed through previous CNF instantiate / upgrade on the nodepools of the cluster. Any manual changes performed directly on the nodes are not preserved.
Applications may face downtime during kubernetes upgrade and may take some time to be available for operations.
Clusters may take some time to be available for operations.
Check and upgrade the required node pools in the Workload cluster.
The IP addresses of master nodes and the worker nodes change after upgrade.
If the upgrade fails, you can correct the configuration and perform the upgrade again.
