NSX Objects Persist After LB Custom Resource Deletion
search cancel

NSX Objects Persist After LB Custom Resource Deletion

book

Article ID: 429178

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • NSX-T LB Virtual Servers remain visible in the NSX Manager UI/API despite the corresponding NSX LB Custom Resource being deleted from Kubernetes/OpenShift
  • Expired or stale SSL certificates remain associated with these ghost Virtual Servers
  • Attempts to delete these objects manually via the UI may fail or be blocked because they are tagged as being managed by NCP

Environment

VMware NSX 

Redhat OpenShift 

 

Resolution

If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.