TKGm 2.5.2 to 2.5.3 Management Cluster Upgrade Triggers Additional Rollout of Management Nodes and All Existing Workload Cluster Nodes

Products

• VMware Tanzu Kubernetes Grid Management

Issue/Introduction

When upgrading the management cluster from TKGm 2.5.2 to 2.5.3, and 2.5.3 to 2.5.4, the following behaviour can be observed:

• Management Cluster

  • The management cluster nodes roll out twice during the upgrade process.

• Workload Clusters

  • All existing workload cluster nodes roll out once.

Environment

TKGm v2.5.2, v2.5.3 

 

Cause

When upgrading management clusters from TKG v2.5.2 to TKG 2.5.3, the management cluster will roll out twice if vspheremachinetemplate has empty fields without values. All existing workload clusters will automatically roll out once to update their vspheremachinetemplate setting. 

Upgrade from 2.5.3 to 2.5.4 will also cause one extra rollout. 

Resolution

The recommended approach is to skip the TKGm 2.5.3 release entirely and upgrade directly from 2.5.2 to 2.5.4.

• For environments upgraded from 2.5.2 to 2.5.3, any empty fields without values in the vspheremachinetemplate will trigger additional rollouts.
• For environments that are already on 2.5.3, there is currently no available workaround to prevent these rollouts when upgrading to 2.5.4.
• The issue is resolved for upgrades after 2.5.4

References: 

Resolved in v2.5.4

VMware Tanzu Kubernetes Grid v2.5.x Release Notes