Unable to create Kubernetes cluster with error " Kubernetes release having '*-zshippable' suffix does not exist, which is required to create a cluster using Cluster API. Contact vSphere administrator to add a compatible Kubernetes release"

Products

• VMware vSphere Kubernetes Service
• VCF Automation

Issue/Introduction

Creation of a Kubernetes cluster via the VMware cloud foundation automation(VCF automation) fails with the following error message:

"Unable to proceed with Create Cluster because the namespace is missing the following resources: Kubernetes releases. You can go back to the service or the namespace page to close this wizard.

Kubernetes release having '-zshippable' suffix does not exist, which is required to create a cluster using Cluster API. Contact the vSphere administrator to add a compatible Kubernetes release."*

This issue is commonly encountered in air-gapped environments where the required Kubernetes releases are not available or have not been manually imported.

Environment

vSphere 7.X

vSphere 8.x

VMware cloud foundation automation(VCF automation)

Cause

This issue may occur due to one or more of the following reasons:

1. The OVA is missing from the content library.

2. The OVA file does not follow the expected naming convention.

3. The content library is not properly synchronized.

4. The content library has not been added as a Kubernetes Service under Supervisor > Configure > General.

Resolution

If none of the following issues are identified or resolved, please open a support case with the Broadcom Support team.

Reference: Create a Local Content Library (for Air-Gapped Cluster Provisioning)

1. OVA Missing in Content Library

Verify that the Tanzu Kubernetes Cluster (TKC) image OVA is present in the content library and accessible.

2. Incorrect Naming Convention for OVA Files

When manually uploading files, ensure that the OVA filename adheres to the expected naming format.
For example, a downloaded TKC image might be named:
ob-18186591-photon-3-k8s-v1.20.7---vmware.1-tkg.1.7fb9067

Only the distribution name portion of the file is needed for import into the local content library.
In this case, the required substring is:
photon-3-k8s-v1.20.7---vmware.1-tkg.1.7fb9067

Note: It is recommended to either save the destination name in a file or keep the browser session open until the process is complete.

Refer to the documentation: Create a Local Content Library (for Air-Gapped Cluster Provisioning)

3. Content Library Synchronization Issues

If the content library was created from the Automation Portal, verify that the sync to vCenter is successful and that the files are visible.
Similarly, if the content library was created directly in vSphere, ensure the information is also reflected accurately in the Automation Portal.

Note: A local library is sufficient for cluster provisioning; a subscribed content library is not required.

4. Content Library Not Added as a Kubernetes Service

Ensure the content library is added under:
Supervisor → Configure → General → Kubernetes Services