VKS Inventory Data is Missing in NSX After Executing NSX Backup and Restore Operations

Products

• VMware vSphere Kubernetes Service
• VMware NSX

Issue/Introduction

After performing an NSX backup and restore operation inventory data from vSphere Kubernetes Service (VKS) clusters is missing or out of sync in the NSX Manager UI. This typically appears in two ways:

1. Missing Clusters: The VKS cluster itself is no longer visible in the NSX Inventory.

2. Missing Objects: The VKS cluster is visible, but specific workloads (such as Pods) created recently are missing from the NSX Inventory.

 

Environment

VKS registered to NSX with Antrea-NSX Interworking enabled.

Cause

This issue occurs because the Antrea-interworking component does not currently have a mechanism to automatically detect when an NSX Manager has been restored to an earlier state. When NSX is restored to a backup, it reverts to a previous state that does not include any inventory updates that occurred after the backup was originally taken, such as new clusters or pods. Due to the Antrea-interworking component only reporting data when a change happens, it does not detect that the NSX inventory is missing information following a  restore. As a result, the inventory remains out of sync until a manual refresh is triggered.

Resolution

To resolve this issue and force a full inventory resync the Antrea-interworking pod must be restarted. Upon restarting, the component will automatically check for the cluster's registration and push all current inventory objects (Clusters, Pods, etc.) back to NSX.

Steps to Restart the Antrea-interworking pod:

1. Log into the cluster where the Antrea-interworking pod is running.

2. Locate the Antrea-interworking pod:

    # kubectl get pods -n <namespace-name> | grep antrea-interworking

3. Delete the Antrea-interworking pod:

    # kubectl delete pod <antrea-interworking-pod-name> -n <namespace-name>

4. After the pod restarts and reaches a Running state log in to the NSX Manager UI and verify that the VKS cluster and its associated pods are now visible in the Inventory.