management cluster context is missing from bootstrap vm on TCA-CP

Products

• VMware Telco Cloud Automation

Issue/Introduction

• Unable to check or switch the context to the management cluster using kubectl commands
• tanzu cli operations fail with the following error message
"unable to fetch the inventory of discovery 'default' for plugins: plugins discovery image resolution failed. Please check that the repository image URL "projects.packages.broadcom.com/tanzu_cli/plugins/plugin-inventory:latest" is correct " 
• Executing kubectl config get-contexts returns no entries for the expected management cluster.

Environment

TCA 3.2
TKG 2.5.2

Cause

The local kubeconfig or Tanzu configuration is missing the context details required to communicate with the management cluster. This context is maintained within specific pods depending on the TKGm version deployed.

Resolution

Retrieve the cluster context directly from the infrastructure pod corresponding to your TKGm management cluster version.

• Verify the Management Cluster Version on the TCA-CP UI.

• Identify the Target Pod

            For Version 1.24.x: The context details are stored in the tkg211 pod.

            For Version 1.28.x: The context details are stored in the tkg252 pod.

• kubectl config get-contexts or tanzu get context command will show the context information