Skip to main content

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. This guide covers operating that shared capacity: reviewing the gateways a data plane manages, assigning more, and understanding how the data plane reconciles each one independently.

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 Dashboard.

Estimated time: 10--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 can be assigned to the data plane through their projects.
  • The independence of gateway reconciliation is understood: one gateway's problem does not block the others.

Prerequisites​

  • Administrator access to the Admin Dashboard, 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​

  1. In the Admin Dashboard, open Data planes and select the data plane.
  2. 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 are assigned to a data plane through their projects, not created on the data plane directly.

  1. Provision a gateway for a project and place it on this data plane, following Provision a gateway for a project.
  2. 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.

Step 3: Understand independent reconciliation​

The data plane reconciles each gateway on its own.

  1. Note that a failure affecting one gateway's assignment does not block the other gateways the data plane manages.
  2. 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.

What to do next​

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.

Plan high availability and disaster recovery

Topology and recovery planning across multiple data planes.