Restoring Endpoint Connectivity to Management Clusters after Upstream Network Changes
search cancel

Restoring Endpoint Connectivity to Management Clusters after Upstream Network Changes

book

Article ID: 448067

calendar_today

Updated On:

Products

VMware Telco Cloud Automation VMware Telco Cloud Platform VMware vSphere Kubernetes Service

Issue/Introduction

  • You are unable to establish a valid connection between the vCenter endpoint and the Tanzu Kubernetes Grid (TKG) management cluster across multiple sites.

  • The vCenter endpoint infrastructure shows a disconnected state

Environment

TCA: 3.4
TCP: 5.1
VKS: 3.2

Cause

This issue occurs when an uncoordinated configuration change on an upstream network router disrupts the routing paths to the endpoints. Even after the network routing is rectified, the vCenter endpoint authentication parameters can become desynchronized. This desynchronization causes the vCenter-to-TKG handshake to fail continuously due to credential rejection.

Resolution

To restore the connection and stabilize the container-to-infrastructure management plane, you must refresh the endpoint credentials to trigger a new authentication handshake.

  1. Log in to the management interface where the endpoints are configured.

  2. Locate the affected vCenter endpoint (e.g., ####).

  3. Update the endpoint credentials with the current valid parameters.

  4. Save the changes to force a re-validation of the vCenter registration with the TKG management cluster.

  5. Verify that the endpoint health status updates