Missing VKS Cluster Metrics in VCF Operations Due to Incorrect Content Library Configuration

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• Administrators may observe that metrics for the VMware Kubernetes Service (VKS) Cluster fail to populate within VMware Cloud Foundation (VCF) Operations.
• When viewing the VKS cluster in the VCF Ops dashboard, the metric displays remain empty.
• In the wcpsvc.log file, errors indicate that the Supervisor version cannot be found in the content catalog:
  
  YYYY-MM-DDT04:00:30.999Z DEBUG wcp 73147 [vc@xx13] [kubelifecycle/kube_instance_interop.go:451] [opID=6a3a1caf-cbf79b48-30e7-4d60-8940-####-###-###] supervisor version v1.32.9+vmware.2-fips-vsc9.1.0.0-25370922 not found in catalog

• Additionally, the WCP logs show that the Content Library (CL) reconciliation is in an error state due to a malformed OVF template name:
  
  YYYY-MM-DDT04:00:26.003Z ERROR wcp 73147 [vc@4413] [content/controller.go:611] [libraryID=8351d840-6296-4525-9ff1-87c6b563d1b6 opID=cl-8351d840-6296-####-########] pre ovf download check failed, err: malformed Supervisor OVF template name 'ob-24076161-ubuntu-2204-amd64-vmi-k8s-v1.30.1---vmware.1-fips-tkg.5'. The template name must be in the format 'supervisor-<supervisor version>'. Example: supervisor-9.1.0.0-25004320
YYYY-MM-DDT04:00:26.011Z DEBUG wcp 73147 [vc@4413] [content/repository.go:187] [opID=cl-8351d840-6296-4525-####-########] Updated stateVector for CL: 8351d840-6296-4525-####-######## to state: APPLY, phase: ERROR, status: ERROR
YYYY-MM-DDT04:00:26.011Z ERROR wcp 73147 [vc@4413] [content/controller.go:196] [opID=svContentWorker-8351d840-6296-4525-####-########] Error reconciling Content Library 8351d840-6296-####-########, err: <nil>

 

Environment

• VMware Cloud Foundation (VCF) 9.x
• VMware Kubernetes Service (VKS)
• vSphere Supervisor Cluster

Cause

The assigned Content Library is incorrectly configured to use a VMware Kubernetes Release (VKR) subscription endpoint instead of the required Supervisor endpoint.

Because the VKR library contains images that do not follow the mandatory supervisor- naming convention, the reconciliation process fails to recognize the OVF templates. This prevents the Supervisor from properly mapping the relationship hierarchy required to pass metrics to the operations dashboard.

Resolution

To resolve this issue, create and assign a new Content Library using the correct Supervisor subscription URL.

1. Navigate to the Content Libraries section in your vSphere Client.

2. Create a new Subscribed Content Library.

3. Configure the subscription URL to point to the official Broadcom Supervisor endpoint: https://wp-content.broadcom.com/supervisor/v1/latest/lib.json

4. Wait for the new Content Library to successfully synchronize.

5. Reassign the newly created and synchronized Content Library to the Supervisor.
   
   

Additional Information

Create a Subscribed Supervisor Content Library for Supervisor Images by Using a Local Content Library.