Back to the archive

The Cloud Relay / Load-tested

Hybrid multi-cloud Kubernetes platform

A K3s cluster spanning an on-premise edge node, AWS, and GCP with secure networking and cloudbursting.

K3sDockerAWSGCPTailscaleCloudflare TunnelsLocust
* CHECK
SUBJECT
Hybrid K3s
TYPE
Cloud infrastructure
STATUS
Load-tested

* 1,000+ concurrent users, 0% failures.

PROOF SIGNAL

1,000+concurrent users, 0% failures

The mission

What the system does

A K3s cluster spanning an on-premise edge node, AWS, and GCP with secure networking and cloudbursting.

  • Cross-cloud overlay networking through Tailscale
  • Secure public exposure with Cloudflare Tunnels
  • Cloudbursting across heterogeneous nodes
  • Distributed Locust performance testing

Engineering log

Decisions behind the build

What the system handles, and why it works this way.

BOSS 01

Network boundaries

Nodes live behind different networks and providers. An encrypted overlay creates stable private connectivity without opening broad inbound access.

BOSS 02

Uneven capacity

Edge and cloud nodes have different resources. Placement and load tests expose where cloudbursting helps rather than merely moving the bottleneck.

System map

How signals move

A plain technical view. The map still works without hovering.

01
Edge controlK3s

Cluster coordination

02
Private meshTailscale

Cross-provider network

03
Burst nodesAWS + GCP

Elastic workload capacity

04
Public gateCloudflare

Secured service exposure

05
Load stationLocust

Distributed validation

LOG ENTRY / WHAT I LEARNED

“Cloud portability is less about identical providers and more about explicit networking, scheduling, and failure assumptions.”

Source signal

Inspect the work.