After an upgrade of vCenter 7.x to vCenter 8.0u3e, the list of compatible Tanzu Kubernetes Releases (TKR) is incorrect.
While connected to the Supervisor cluster context, checking the list of TKRs returns the following incompatible TKRs as compatible True:
kubectl get tkr
v1.23.15---vmware.1 v1.23.15+vmware.1 False False
v1.23.8---vmware.1-tkg.1 v1.23.8+vmware.1-tkg.1 False False
v1.24.9---vmware.1 v1.24.9+vmware.1 False False
v1.25.7---vmware.3-fips.1 v1.25.7+vmware.3-fips.1 True True
v1.26.13---vmware.1-fips.1 v1.26.13+vmware.1-fips.1 True True
v1.26.5---vmware.2-fips.1 v1.26.5+vmware.2-fips.1 True True
v1.27.11---vmware.1-fips.1 v1.27.11+vmware.1-fips.1 True True
kubectl get kr
v1.23.15---vmware.1 v1.23.15+vmware.1 False False
v1.23.8---vmware.1-tkg.1 v1.23.8+vmware.1-tkg.1 False False
v1.24.9---vmware.1 v1.24.9+vmware.1 False False
v1.25.7---vmware.3-fips.1 v1.25.7+vmware.3-fips.1 False False
v1.26.13---vmware.1-fips.1 v1.26.13+vmware.1-fips.1 False False
v1.26.5---vmware.2-fips.1 v1.26.5+vmware.2-fips.1 False False
v1.27.11---vmware.1-fips.1 v1.27.11+vmware.1-fips.1 False False
Environment where it was recently upgraded from vSphere with Tanzu 7 to vSphere with Tanzu 8
Post-upgrade of any vCenter 7 version to vCenter 8.0u3e
VKS/TKG Service v3.2 and higher
This issue can occur regardless of whether or not the cluster is managed by Tanzu Mission Control (TMC)
Starting in vSphere 8.0, the VKS/TKG Service as a Supervisor Service manages compatibility of Kubernetes Releases.
Consult the output of Kubernetes Releases (KR) for accurate compatibility of vSphere Kubernetes workload cluster versions.
kubectl get kr