blueprint · described

GCP and AWS through a transit cluster

A cluster in each cloud, joined through a transit cluster. The headline shape of the product, set out so you can see where it is going. None of it runs today.

Not operating yet

Clusters do not connect to each other, and the AWS integration is not implemented. This page describes a proposed model. It is not a design we have committed to, and not something you can build today.

The proposed shape

The multi-region model with the regions in different clouds: a local cluster in GCP, a local cluster in AWS, and a transit cluster between them. The gateways already reach each other over WireGuard between public addresses, which does not care which provider an address belongs to — so the joining problem is the same one as multi-region, not a separate one.

What has to exist first

Everything the multi-region blueprint is waiting on.
An AWS integration. Every AWS operation is unimplemented today, and an AWS account cannot yet validate.
An AWS equivalent of the spoke attachment, which is expected to be a different construct from a GCP peering and is not yet decided.

routing…