The Supervisor Cluster deployment becomes stuck in a "Not Ready" state
search cancel

The Supervisor Cluster deployment becomes stuck in a "Not Ready" state

book

Article ID: 433601

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In VMware Cloud Foundation (VCF) 9.0.1, when deploying a new vSphere Kubernetes Service (VKS) cluster via VCF Automation (VCFA), the Supervisor Cluster deployment becomes stuck in a "Not Ready" state.

Environment

VCF Automation 9.x
vSphere Kubernetes Service 9.x

Cause

The "Assign to all current and future namespaces" option is not enabled within the VCFA Content Hub configuration for the specific Content Library.

Resolution

To ensure Content Libraries are automatically attached to all Supervisor Clusters and namespaces, follow these steps:

  1. Log in to the VCF Automation (VCFA) interface.

  2. Navigate to Build & Deploy > Content Hub > Content Libraries.

  3. Select the Content Library intended for use with VKS/Supervisor Clusters.

  4. Locate and enable the toggle or checkbox for "Assign to all current and future namespaces".

  5. Verify that Region Mappings are correctly defined for all applicable regions within the Content Hub to ensure the library is accessible to the target Supervisor Clusters.

  6. Once enabled, new Supervisor Cluster deployments will automatically attach the library and transition to a "Ready" state.

 

Powered by Wolken Software