TKR Version Retrieval Fails with the error: “No resources found” After Content Library Change in VMware Kubernetes Service
search cancel

TKR Version Retrieval Fails with the error: “No resources found” After Content Library Change in VMware Kubernetes Service

book

Article ID: 416709

calendar_today

Updated On:

Products

VMware vSphere Kubernetes Service

Issue/Introduction

After switching to a newly created content library in a vSphere Supervisor Cluster, users may encounter the following error when attempting to retrieve Tanzu Kubernetes Release (TKR) versions:

Warning: run.tanzu.vmware.com/tanzukubernetesrelease is deprecated. It is succeeded by kubernetes.vmware.com/kubernetesrelease. Refer to documentation. No resources found

This issue prevents the Supervisor Cluster from discovering available TKR versions, impacting cluster provisioning and lifecycle operations.

Environment

VMware vSphere Kubernetes Service

Cause

The issue occurs when the new content library is populated by cloning items from an existing library. Content library items retain metadata that links them to their original source. This metadata mismatch disrupts the resource discovery process for TKR versions.

In air-gapped environments, improper cloning of content library items can lead to broken associations, resulting in the failure to fetch TKR metadata.

Resolution

To resolve the issue:

1. Rollback to the Original Content Library: Revert the Supervisor Cluster to use the original content library where TKR versions were previously accessible. This restores the correct metadata associations and resolves the resource discovery failure.

2. Follow Official Procedures for Content Library Management: When creating or updating content libraries—especially in air-gapped environments—ensure that the process aligns with Broadcom’s documented best practices.

Additional Information