Manage multiple gateways on a data plane
Enterprise Tier
A data plane is shared provisioning capacity: one data plane can provision and manage many gateways at once, each serving a single project.
Each gateway on a data plane has its own customer-facing URL and serves exactly one project, so a request to a gateway URL always resolves to a single project's configuration. The data plane provisions the runtime for each gateway and keeps it aligned with the desired configuration the management plane publishes. Because gateways are reconciled independently, they can be added, changed, and recovered without affecting one another.
Persona: Platform operator with data-plane operations access, working in the Admin Console.
Estimated time: 10 to 15 minutes.
Outcomes
By the end of this guide:
- The gateways a data plane manages can be reviewed, with their URL, owning project, configuration version, and health.
- Additional gateways appear on the data plane when more projects select it.
- The independence of gateway reconciliation is understood: one gateway's problem does not block the others.
Prerequisites
- Administrator access to the Admin Console, with data-plane operations permissions.
- A data plane deployed and registered. See Deploy and register a data plane.
Step 1: review the gateways a data plane manages
- In the Admin Console, open Data planes and select the data plane.
- Review the gateways it manages. For each gateway, the view shows the customer-facing URL, the owning project, the configuration version applied, and the gateway's health.
The management plane tracks whether the desired configuration version is applied per gateway, so a gateway that has not yet caught up with a recent change is visible as such.
Step 2: assign more gateways to the data plane
Gateways appear on a data plane when their projects select that data plane. There is no top-level Gateways menu for creating gateways separately, and gateways are not created on the data plane directly.
- On a project, select this data plane so its gateway is auto-provisioned here, following Provision a gateway for a project.
- Confirm the new gateway appears among those the data plane manages.
A single data plane can host many projects' gateways this way, which is how several teams share one deployment while each keeps its own isolated endpoint.
Each of those endpoints carries its own hostname, and hostnames are not shared between gateways, so every project added to a data plane needs a further hostname exposed on its ingress with DNS and certificate coverage. A data plane installed with one hostname serves one project until that work is done. See Each project gateway needs its own hostname.
Step 3: understand independent reconciliation
The data plane reconciles each gateway on its own.
- Note that a failure affecting one gateway's assignment does not block the other gateways the data plane manages.
- Use the per-gateway health and configuration-version indicators to isolate a problem to a single gateway rather than the whole data plane.
Spreading traffic across several data planes, rather than several gateways on one, is covered in Load balance across regional deployments. That pattern is about capacity and backends across regions. Separately, when a single project optionally attaches several like-configured gateways for high availability behind customer-managed DNS, see Gateway sets and DNS-level failover. That is not the same as many projects sharing one data plane.
Where to go next
Migrate a gateway or upgrade its runtime
Move a gateway between data planes, or upgrade in place, with a stable URL.
Gateway sets and DNS-level failover
Optional Enterprise HA for several members of the same project.
Understand guardrail enforcement on shared capacity
When several projects' gateways share one data plane, each project's guardrails apply only to its own traffic, and gateway attachment health determines what is enforced.
Plan high availability and disaster recovery
Topology and recovery planning across data planes.