Aria Automation kublet version may differ when joining new appliance to existing previously upgraded appliances

Products

• VMware Aria Suite

Issue/Introduction

• Kublet version may differ when joining newer appliance to existing previously upgraded appliances.
• Running the kubectl get nodes command you see a minor discrepancy in the version name of a newly deployed node:

NAME STATUS ROLES AGE VERSION

AriaAutoNode1FQDN Ready control-plane,master 6d v1.20.11-1+1f8a47eae6d024-dirty
AriaAutoNode2FQDN Ready control-plane,master 12d v1.20.11-dirty
AriaAutoNode3FQDN Ready control-plane,master 12d v1.20.11-dirty

Environment

VMware vRealize Automation 8.x

Resolution

The behaviour is a result of the way Kubernetes handles upgraded nodes compared to new nodes, For upgraded nodes it keeps old version name when there is no change in major.minor.patch numbers The issue is cosmetic and can be safely ignored.