This topic describes upgrade scenarios for VMware Tanzu Kubernetes Grid Integrated Edition (TKGI) environments that are upgraded from v1.16 to v1.17 on vSphere.

Overview

When you upgrade TKGI on vSphere, you might also upgrade vSphere and, if you are using it, NSX.

TKGI, NSX, and vSphere upgrades depend on each other. Some combinations also require upgrading VMware Tanzu Operations Manager (Ops Manager) or TKGI-provisioned Kubernetes clusters.

For any combination of upgrades that you perform, you must follow the upgrade order described in this topic.

TKGI on vSphere with NSX Networking

When upgrading a TKGI environment on vSphere with NSX networking, you can choose to upgrade any of the following:

  • TKGI only, optionally including Kubernetes clusters
  • TKGI, Kubernetes clusters, and NSX
  • TKGI, Kubernetes clusters, NSX, and vSphere

For more information, see below:

To upgrade these components… Use this order… For more information, see…
TKGI
  1. Upgrade Ops Manager if necessary.
  2. Upgrade TKGI.
  3. (Recommended) Upgrade Kubernetes clusters.
 Upgrading to TKGI v1.17
TKGI and NSX
  1. Upgrade NSX.

  2. Upgrade Ops Manager if necessary.
  3. Upgrade TKGI.
  4. Upgrade Kubernetes clusters.
 Upgrading to TKGI v1.17 and NSX v4.0
TKGI, NSX, and vSphere
  1. Upgrade NSX.

  2. Upgrade Ops Manager if necessary.
  3. Upgrade TKGI.
  4. Upgrade Kubernetes clusters.
  5. Upgrade vSphere.
 Upgrading to TKGI v1.17, NSX, and vSphere v8.0

Warning: Refer to the Release Notes for current version support, known issues, and other important information.

For a list of NSX and vSphere versions compatible with Tanzu Kubernetes Grid Integrated Edition v1.17, see:

Scenario 1: Upgrading to TKGI v1.17

In this upgrade scenario, you upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17 and do not upgrade your NSX or vSphere infrastructure.

The upgrade scenario includes the following steps:

  1. Upgrade Ops Manager to v2.10.59 or later. These are the recommended Ops Manager versions for Tanzu Kubernetes Grid Integrated Edition v1.17.0. To verify Ops Manager compatibility with other v1.17 versions, see Retrieve Product Version Compatibilities from the Tanzu API in the Broadcom Support KB.
  2. Upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17.
  3. If you are upgrading a cluster that uses a public cloud CSI driver, see Limitations on Using a Public Cloud CSI Driver in Release Notes for additional requirements.
  4. (Recommended) Upgrade all Kubernetes clusters to Tanzu Kubernetes Grid Integrated Edition v1.17. This upgrades the NCP version of your clusters.

See the table below for version information and instructions for this upgrade scenario:

Component Pre-upgrade version Post-upgrade version Instructions
TKGI v1.16 v1.17 See Upgrading Tanzu Kubernetes Grid Integrated Edition (NSX Networking).
Ops Manager v2.10.53 v2.10.59 or v3.0.12 n/a

Scenario 2: Upgrading to TKGI v1.17 and NSX v4.0

Warning: Refer to the Release Notes for current version support, known issues, and other important information.

In this upgrade scenario, you upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17 and NSX from v3.2, to v4.0.1 or later.

The upgrade scenario includes the following steps:

  1. Upgrade NSX from v3.2.1 or later to v4.0.1 or later.
  2. Upgrade Ops Manager to v2.10.59 or later. These are the recommended Ops Manager versions for Tanzu Kubernetes Grid Integrated Edition v1.17.0. To verify Ops Manager compatibility with other v1.17 versions, see Retrieve Product Version Compatibilities from the Tanzu API in the Broadcom Support KB.
  3. Upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17.
  4. If you are upgrading a cluster that uses a public cloud CSI driver, see Limitations on Using a Public Cloud CSI Driver in Release Notes for additional requirements.
  5. Upgrade all Kubernetes clusters to Tanzu Kubernetes Grid Integrated Edition v1.17. This upgrades the NCP version of your clusters.

See the table below for version information and instructions for this upgrade scenario:

Component Pre-upgrade version Post-upgrade version Instructions
TKGI v1.16 v1.17 See Upgrading Tanzu Kubernetes Grid Integrated Edition (NSX Networking).
Ops Manager v2.10.53 v2.10.59 or v3.0.12 n/a
NSX v3.2.1 or later v4.0.1 or later
NCP v4.1.0 v4.1.1.0 n/a

Scenario 3: Upgrading to TKGI v1.17, NSX v4.0, and vSphere v8.0

Warning: Refer to the Release Notes for current version support, known issues, and other important information.

In this upgrade scenario, you upgrade:

  • Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17
  • NSX from v3.2.2 or later to v4.0.1 or later.
  • vSphere from v7.0 to v8.0

The upgrade scenario includes the following steps:

  1. Upgrade NSX from v3.2.2 or later, to v4.0.0. or later.
  2. Upgrade Ops Manager to v2.10.59 or later. These are the recommended Ops Manager versions for Tanzu Kubernetes Grid Integrated Edition v1.17.0. To verify Ops Manager compatibility with other v1.17 versions, see Retrieve Product Version Compatibilities from the Tanzu API in the Broadcom Support KB.
  3. Upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17.
  4. If you are upgrading a cluster that uses a public cloud CSI driver, see Limitations on Using a Public Cloud CSI Driver in Release Notes for additional requirements.
  5. Upgrade all Kubernetes clusters to Tanzu Kubernetes Grid Integrated Edition v1.17. This upgrades the NCP version of your clusters.
  6. Upgrade vSphere from v7.0 to v8.0.

See the table below for version information and instructions for this upgrade scenario:

Component Pre-upgrade version Post-upgrade version Instructions
TKGI v1.16 v1.17 See Upgrading Tanzu Kubernetes Grid Integrated Edition (NSX Networking).
Ops Manager v2.10.53 v2.10.59 or v3.0.12 n/a
NSX v3.2.2 or later v4.0.1 or later See Upgrade NSX Data Center to v4.0.1 in Upgrading Tanzu Kubernetes Grid Integrated Edition (NSX Networking).
NCP v4.1.0 v4.1.1.0 or later n/a
vSphere v7.0 v8.0

See the vSphere documentation:

  1. Upgrading the vCenter Server Appliance
  2. Upgrading ESXi Hosts
Also, see Overview of the vSphere Upgrade Process.

TKGI on vSphere (Antrea and Flannel Networking)

When upgrading a Tanzu Kubernetes Grid Integrated Edition environment on vSphere with Antrea or Flannel networking, you can choose to upgrade any of the following:

  • TKGI only, optionally including Kubernetes clusters
  • TKGI, Kubernetes clusters, and vSphere

For more information, see below:

To upgrade these components… Use this order… For more information, see…
TKGI
  1. Upgrade Ops Manager if necessary.
  2. Upgrade TKGI.
  3. (Recommended) Upgrade Kubernetes clusters.
 Upgrading to TKGI v1.17
TKGI and vSphere
  1. Upgrade Ops Manager if necessary.
  2. Upgrade TKGI.
  3. Upgrade Kubernetes clusters.
  4. Upgrade vSphere.
 Upgrading to TKGI v1.17 and vSphere v7.0

For a list of vSphere versions compatible with Tanzu Kubernetes Grid Integrated Edition v1.17, see VMware Product Interoperability Matrices.

Scenario 1: Upgrading to TKGI v1.17

In this upgrade scenario, you upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17 and do not upgrade your vSphere infrastructure.

The upgrade scenario includes the following steps:

  1. Upgrade Ops Manager to v2.10.59 or later. These are the recommended Ops Manager versions for Tanzu Kubernetes Grid Integrated Edition v1.17.0. To verify Ops Manager compatibility with other v1.17 versions, see Retrieve Product Version Compatibilities from the Tanzu API in the Broadcom Support KB.
  2. Upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17.
  3. If you are upgrading a cluster that uses a public cloud CSI driver, see Limitations on Using a Public Cloud CSI Driver in Release Notes for additional requirements.
  4. (Recommended) Upgrade all Kubernetes clusters to Tanzu Kubernetes Grid Integrated Edition v1.17. This upgrades the NCP version of your clusters.

See the table below for version information and instructions for this upgrade scenario:

Component Pre-upgrade version Post-upgrade version Instructions
TKGI v1.16 v1.17 See Upgrading Tanzu Kubernetes Grid Integrated Edition (Antrea and Flannel Networking).
Ops Manager v2.10.53 v2.10.59 or v3.0.12 n/a
vSphere v7.0 v7.0 n/a

Scenario 2: Upgrading to TKGI v1.17 and vSphere v8.0

In this upgrade scenario, you upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17 and vSphere from v7.0 to v8.0.

The upgrade scenario includes the following steps:

  1. Upgrade Ops Manager to v2.10.59 or later. These are the recommended Ops Manager versions for Tanzu Kubernetes Grid Integrated Edition v1.17.0. To verify Ops Manager compatibility with other v1.17 versions, see Retrieve Product Version Compatibilities from the Tanzu API in the Broadcom Support KB.
  2. Upgrade Tanzu Kubernetes Grid Integrated Edition from v1.16 to v1.17.
  3. Upgrade all Kubernetes clusters to Tanzu Kubernetes Grid Integrated Edition v1.17. This upgrades the NCP version of your clusters.
  4. Upgrade vSphere from v7.0 to v8.0.

See the table below for version information and instructions for this upgrade scenario:

Component Pre-upgrade version Post-upgrade version Instructions
TKGI v1.16 v1.17 See Upgrading Tanzu Kubernetes Grid Integrated Edition (Antrea and Flannel Networking).
Ops Manager v2.10.53 v2.10.59 or v3.0.12 n/a
vSphere v7.0 v8.0

See the vSphere documentation:

  1. Upgrading the vCenter Server Appliance
  2. Upgrading ESXi Hosts
Also, see Overview of the vSphere Upgrade Process.

check-circle-line exclamation-circle-line close-line
Scroll to top icon