Kubernetes adapter instance (AI) is not automatically created by Tanzu Mission Control (TMC) adapter

Products

• VMware Aria Suite

Issue/Introduction

When a Kubernetes adapter instance is manually removed, upon restarting the Tanzu Mission Control (TMC) adapter, the deleted adapter instance doesn't get automatically recreated.

Environment

Aria Operations 8.18

Cause

The TMC adapter reads all the clusters in inventory and automatically creates a Kubernetes adapter instance (AI) for every cluster.  When a Kubernetes adapter instance (AI) is manually removed from Aria Operations, the associating credential also needs to be cleaned up and removed.  Since the orphaned credential existed, it prevents TMC to rediscover and recreate the adapter instance.

Resolution

Clean up the orphaned adapter instance credential and restart TMC adapter collection.

• On Aria Operations UI, go to "Administration/Integrations"
• Click on "Credentials"

• Identify the credential for the manually deleted Kubernetes adapter instance (AI).
• Properly remove it.
• Go back to Integrations, restart the collection for the TMC adapter. 

• Once the TMC adapter is restarted, upon rediscovery, the existing Kubernetes cluster will be added as a new Kubernetes adapter instance (AI) on Aria Operations.