The config cluster is the single source of multi-cluster Gateway intent

Member clusters join a fleet, but Gateway and HTTPRoute objects live in one designated config cluster. The controller discovers exported services and programs one load-balancing view.

1Register fleetClusters become members of one fleet trust boundary.

2Choose config clusterOne member hosts Gateway API configuration.

3Export servicesBackends become discoverable across member clusters.

4Reconcile globallyThe multi-cluster controller programs the selected load balancer.

5Route around failureHealthy backends in remaining clusters continue serving.

Do not duplicate the Gateway manifest into every member cluster.

The config cluster is the single source of multi-cluster Gateway intent

Multi-cluster Gateway is easiest to understand by separating the Kubernetes contract from the Google Cloud implementation. GKE's multi-cluster controller reads configuration from a designated config cluster and uses fleet membership plus multi-cluster services to discover backends. The Kubernetes objects stay familiar, but GKE supplies controllers, infrastructure and safe defaults around them. This is why a team can move from an on-premises cluster without rewriting every workload, while still needing to redesign networking, identity and operational ownership for the cloud environment.

A useful inspection step is `gcloud container fleet ingress describe`. Read the output as evidence, not as a ritual: first confirm the desired object exists, then look at status conditions, events and the Google Cloud resource it represents. In production, capture the expected result in a runbook or automated check so an operator can distinguish slow reconciliation from a configuration error.

Production gotcha: The config cluster is a control dependency; protect its access and keep its declarations in version control even though traffic can use other clusters. The safe habit is to verify quotas, regional availability and feature support against current Google Cloud documentation before rollout. Inference Gateway applies the same model to AI routing.