The VMware vSphere Kubernetes releases (VKr) Lifecycle and how to review the End of Service status of Kubernetes Releases

Products

• Tanzu Kubernetes Runtime
• VMware vSphere Kubernetes Service
• VMware Tanzu Kubernetes Grid
• VMware Tanzu Kubernetes Grid Management

Issue/Introduction

This article provides the following details:

• VKr (TKGs) – Managing End of Service of Kubernetes versions

Outlines the The vSphere Kubernetes Support Lifecycle of vSphere Kubernetes releases (VKr) (formerly known as Tanzu Kubernetes releases or TKr) 

• Accessing Broadcom Product Lifecycle page
  
  
  
• How to view the vSphere Kubernetes Releases and their End of Service status

Environment

VMware vSphere with Tanzu

VMware Tanzu Kubernetes Grid

Resolution

• VKr (TKGs) – Managing End of Service of Kubernetes versions

Outlines the The vSphere Kubernetes Support Lifecycle of vSphere Kubernetes releases (VKr) (formerly known as Tanzu Kubernetes releases or TKr) 

Refer to VKr (TKGs) – Managing End of Service of Kubernetes versions.  This outlines the vSphere Kubernetes Support Lifecycle.

 

• Accessing Broadcom Product Lifecycle page

1. 1. Login to the Broadcom Support portal
      
      
   2. Navigate to the Broadcom Product Lifecycle page

 

• How to view the vSphere Kubernetes Releases and their End of Service status

NOTE: Some account views may not be able to view the product vSphere Kubernetes Releases by default.  Follow these steps.

While viewing the Product Lifecycle page:

• • • Make sure you have selected the VMware Cloud Foundation in the Select Division dropdown.

Example: You should show the following selected

 

 

• • • Then type vSphere Kubernetes Releases in the Search Product Name box
      
      
    • Then select the vSphere Kubernetes Releases from the menu
      
      

Example:  You should show the following:

 

 

• • • Then click the Show Results box

Example:

 

 

 

Additional Information

Broadcom Maintenance Policy Handbook

Use the following commands to confirm current version 

While connected from the Supervisor cluster context:
kubectl get tkc,cluster -n <workload cluster namespace>
kubectl get machines -n <workload cluster namespace>

While connected from the workload cluster's context:
kubectl get nodes