This article explains why the cf connected-clusters command may return an empty list, even when clusters are visible in the Tanzu Hub user interface, and provides steps to troubleshoot visibility issues.
When executing the cf connected-clusters command via the Tanzu cf CLI, the console returns an empty list, despite the user being able to see active clusters within the Tanzu Hub UI.
cf CLI pluginThis behavior is expected if the resources viewed in the UI are "Foundations" or clusters associated with k8s-based data tiles. The cf connected-clusters command is specifically designed to retrieve Kubernetes clusters that are explicitly enrolled as "Connected Clusters" in Tanzu Hub (e.g., TKG, vSphere with Tanzu, AWS EKS, Azure AKS, Google GKE, or generic CNCF Kubernetes clusters). It does not function as a general inventory tool for all platform assets.
If you are unable to see your Kubernetes clusters, please verify the following configurations:
cf CLI user profile is authenticated to the correct tenant and organization that manages the target clusters.