Prerequisites and Upgrade Steps for Rolling Upgrade of Tanzu Kubernetes Workload Clusters to version 1.33.3 on vSphere Supervisor Clusters

Products

• Tanzu Kubernetes Runtime

Issue/Introduction

A rolling upgrade of a Tanzu Kubernetes Cluster managed by vSphere Supervisor to Kubernetes version v1.33.3 is planned. The current environment details are:

• Supervisor Cluster: v1.30.10+vmware.1-fips-vsc0.1.12-24799161
• vCenter: vCenter Server 8.0 Update 3g
• Kubernetes Service (VKS): 3.3.3-embedded

The question is whether any additional prerequisites or specific upgrade steps are required in this environment to support the rolling upgrade to v1.33.3 beyond the standard TKG cluster upgrade procedures.

Environment

VMware Kubernetes Service

Resolution

The upgrade step and any specific prerequisites for rolling upgrades to Kubernetes v1.33.3 on vSphere Supervisor Clusters are primarily determined by the cluster class of the TKG cluster being upgraded (v1beta1 or v1alpha3).

1. Determine the Cluster Class:

Identify whether the TKG cluster targeted for upgrade is using the v1beta1 or v1alpha3 API version for its cluster definition. This can typically be found within the cluster's manifest or by inspecting the cluster object using the command "kubectl get clusters -A".

2. Follow the Relevant Upgrade Documentation:

For v1beta1 TKG Clusters:

If the TKG cluster is defined using the v1beta1 API, follow the instructions provided in the official Broadcom documentation titled: "Update a v1beta1 TKG Cluster by Editing the TKr Version." This document outlines the specific steps and considerations for upgrading TKG clusters utilizing the v1beta1 cluster class.

For v1alpha3 TKG Clusters:

If the TKG cluster is defined using the v1alpha3 API, follow the instructions provided in the official Broadcom documentation titled: "Update a v1alpha3 TKG Service Cluster by Editing the TKr Version." This document details the specific procedures for upgrading TKG Service clusters utilizing the v1alpha3 cluster class.