Anthos multi-cluster management offers a set of capabilities that help you and your organization (such as from infrastructure operators and workload developers/operators to security and network engineers) manage clusters, infrastructure, and workloads across cloud and on-premises environments. This page describes our expanding portfolio of multi-cluster management capabilities and provides resources to get started.
Connect allows you to connect your Anthos GKE deployed on-prem and other Kubernetes clusters to Google Cloud.
To learn more about Connect, refer to the Connect overview.
Google Cloud Console
Google Cloud Console (Cloud Console) provides a central user interface for managing all of your Kubernetes clusters no matter where they are running. After you have registered your Kubernetes clusters with Cloud Console, you can log in to view, monitor, debug, and manage their workloads.
To learn more and to get started, refer to the Cloud Console page.
Anthos Config Management
Anthos Config Management allows cluster operators to manage configurations across multiple clusters and environments using files stored in a Git repository. To learn more and get started, refer to the Anthos Config Management documentation.
About connecting and registering Kubernetes clusters
To provide multi-cluster management from Google Cloud, many features require that your clusters be registered to your Google Cloud project. After registration, products like Cloud Console connect to your clusters and provide the services you enable across your clusters.
To connect Anthos GKE deployed on-prem and other Kubernetes clusters residing outside of your Google Cloud project, Google provides a "Connect agent," a Kubernetes Deployment resource that you run in your clusters. Many multi-cluster features rely on this piece of infrastructure. The Connect agent reaches out to Google to establish a connection to your project. It can traverse NATs, egress proxies, VPNs, and other interconnects you have between your other environments and Google. Additionally, your Kubernetes clusters and their API servers do not need public or externally exposed IPs.
To learn more about the Connect agent, see the refer to the Connect documentation.