Operational Defect Database
BugZero updated this defect 54 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 96992
'no matches for kind "MachineHealthCheck" in version " http://cluster.x-k8s.io/v1beta2' error when Node Health Check is activated on Tanzu Kubernetes Grid clusters in Cloud Director
Last update date:
3/26/2024
Affected products:
Cloud Director
Affected releases:
10.5
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Creating and editing Tanzu Kubernetes Grid clusters using Container Service Extension for Cloud Director.Creating clusters with Node Health Check activated, or activating Node Health Check for existing clusters causes the cluster to become unmanageable.When viewing Events for Tanzu Kubernetes Grid clusters with Node Health Check activated in the Kubernetes Container Clusters plugin in the Cloud Director UI, errors similar to the following are seen: Event Details Name: PatchObjectError Type: Error Time: <DATE> Resource Name: MachineHealthCheck/<CLUSTER_NAME> error: [no matches for kind "MachineHealthCheck" in version "cluster.x-k8s.io/v1beta2"] during patching objects with name [MachineHealthCheck/<CLUSTER_NAME>]
Cause
This error is caused by Kubernetes Container Clusters UI plugin 4.2 creating the MachineHealthCheck capi yaml object with an invalid apiVersion value. Clusters that contain this invalid MachineHealthCheck section become unmanageable.
Resolution
This issue is resolved in Kubernetes Container Clusters UI Plugin 4.2.1 available from VMware Downloads.For more information see the VMware Cloud Director Container Service Extension 4.2.1 Release Notes. After upgrading to VMware Cloud Director Container Service Extension 4.2.1 and Kubernetes Container Clusters UI Plugin 4.2.1, users can create new clusters with Node Health Check activated. For existing clusters affected by this issue, after upgrading to Kubernetes Container Clusters UI Plugin 4.2.1 Node Health Check can be toggled on or off to fix the cluster's capi yaml and resolve this issue.
