VMware Telco Cloud Automation is integrated with VMware Tanzu Kubernetes Grid. To upgrade Tanzu Kubernetes Grid from 2.1.1, 2.5, or 2.5.1 to 2.5.2, you must first upgrade the Tanzu Kubernetes management clusters and then the Tanzu Kubernetes workload clusters.

If Tanzu Kubernetes clusters are deployed in an airgap environment, ensure that the airgap server is upgraded first.

For information about the Kubernetes upgrade compatibility for clusters, see:

Procedure

  1. Download the latest version of the Kubernetes Cluster templates that you use to upgrade the Tanzu Kubernetes cluster.

    To download Tanzu Kubernetes Grid, see Drivers & Tools on the Telco Cloud Platform RAN Essentials 5.0 product downloads page.

  2. Import the Kubernetes Cluster OVA into vSphere where the Tanzu Kubernetes cluster is located, and convert the OVA into a template.
  3. Upgrade the Tanzu Kubernetes management cluster. For instructions, see Upgrade the Kubernetes Version for a Cluster Instance.

    Repeat Step 3 to upgrade each Tanzu Kubernetes management cluster sequentially.

  4. Upgrade the Tanzu Kubernetes workload clusters. For instructions, see Upgrade Kubernetes Version for Workload Cluster Instance.

    Repeat Step 4 to upgrade each Tanzu Kubernetes workload cluster.

Results

VMware Tanzu Kubernetes Clusters are upgraded successfully. All pods in the cluster are up and running.

Important! (Applies to both PTP timing pod and Systemd deployments) During the Kubernetes workload cluster upgrade, the DU worker node is deleted and re-created with the same label on the same host. This causes the deletion of PTP timing solution deployed in the worker node and the sidecar database associated with PTP subscription. Hence, the existing PTP subscription becomes invalid after the upgrade. The DU application must re-register and subscribe to the PTP notification after the Tanzu Kubernetes Cluster upgrade.

What to do next

  1. Update the Kubernetes template version:

    1. In the Telco Cloud Automation UI, navigate to Infrastructure > CaaS Infrastructure > Cluster templates.

    2. Edit the templates that show compatibility errors.

    3. Change the Kubernetes version to the latest one.

  2. Ensure that the DU application is re-registered and subscribed to the PTP notification.