Antrea cluster inventory appears in Default NSX project instead of Supervisor project

Products

• VMware NSX

Issue/Introduction

Antrea clusters deployed to VPCs under a non-default NSX project do not appear in that specific project's inventory within the NSX Manager UI. Instead, the clusters and their associated Kubernetes resources are found only under the Default NSX project inventory.

Symptoms:

• Supervisor is connected to a non-default NSX project (e.g., ####-distributed).
• vSphere Namespaces and VPCs are correctly created under the custom project.
• Antrea clusters deployed within these VPCs are missing from the custom project's Inventory tab.
• Resources are visible to Enterprise Administrators in the Default (Global) project.
• Project Administrators cannot view their own Antrea clusters or internal resources (Pods/Services).

Environment

• VMware Cloud Foundation 9.x / 5.x
• VMware NSX 4.x / 9.x
• Antrea v2.5.1 and higher

Cause

In the current NSX multi-tenancy architecture, Kubernetes inventory synchronization for Antrea clusters is designed to sync exclusively to the Default Project (Global Inventory). While the networking (VPC) resides in the custom project, the high-level Kubernetes resource visibility is maintained at the global level.

Resolution

This is expected operational behavior per official multi-tenancy design specifications. No configuration changes are required.

To view Antrea cluster resources in the NSX Manager UI, use an account with one of the following:

1. Enterprise Administrator privileges.
2. Global inventory permissions that grant access to the Default Project.

For more information on supported features within projects, see   Features Available for Consumption Under NSX Projects..