Supervisor Cluster in Configuring State Due to Missing Root Namespaces Resource Pool

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

The Supervisor Cluster remains indefinitely in a "Configuring" state. A split-brain condition exists where the Kubernetes control plane retains the namespace inventory, but the vCenter Server inventory is missing the corresponding Namespaces resource pool (vim.ResourcePool:resgroup-xxxxx).

 

From vSphere UI, when you click on the Configuring Supervisor you see the following error

Initialized vSphere Resources
Resource Type ResourcePool, Identifier resgroup-xxxxx is not found.

Cause

Condition has been observed following ungraceful datacenter events, such as a sudden power failure, which can cause the vCenter Server inventory to lose the Namespaces resource pool while the Kubernetes control plane retains its respective inventory.

Resolution

Engage Broadcom Technical Support to recover the missing resource pool and resolve the split-brain state.