Providers¶
Tomoda spans five providers. Each has a specific job; they do not overlap.
| Provider | Responsibility |
|---|---|
| OVH | Compute: one Rise bare-metal server in Beauharnois running k3s and every workload |
| Cloudflare | DNS, edge proxy for the prod app, Workers (media CDN, OG previews, synthetic probes), Tunnel for loki-push, all object storage (R2) |
GCP (project development-485000) |
Secret Manager, the Terraform state bucket, Google OAuth clients, Places API billing, the fastlane match certs bucket. No compute |
| GitHub | Source, CI (Actions + in-cluster ARC runners), container images (GHCR), org and repo settings (infrastructure/github/) |
| Tailscale | Private admin network to the server (SSH, kube-apiserver); policy in infrastructure/tailscale/ |
OVH: workloads¶
Everything that runs or holds data lives on the k3s server: the app, Postgres (CNPG), Redis, Photon, NATS, monitoring and Argo CD. Node bootstrap and k3s config are in scripts/ovh/. See OVH bare metal.
Cloudflare: edge and storage¶
Terraform in infrastructure/cloudflare/:
- DNS: app records are written by external-dns from Ingress resources; the app hosts are proxied, and prod is origin-locked with authenticated origin pulls.
- Workers:
tomoda-assets-{dev,prod}(media from R2 with signed URLs),tomoda-og-preview,tomoda-synthetic. - R2: media, CNPG backups, Loki/Tempo, OTA bundles, the Photon index and seed sets. Free egress, so restores and index pulls cost nothing.
See Cloudflare.
GCP: secrets and identity only¶
- Secret Manager is the source for every ExternalSecret; ESO authenticates with a scoped service-account key.
- tfstate bucket
tomoda-tfstateholds Terraform state for every stack (cloudflare, gcp, gcp-org, github, tailscale). - Google OAuth clients back Sign in with Google, Argo CD Dex, oauth2-proxy and Grafana.
-
Places API calls from the backend bill to this project.
-
Org IAM and billing budgets for the
tomoda.lifeorganization.
Terraform in infrastructure/gcp/ and infrastructure/gcp-org/. See GCP and GCP organization.
Putting it together¶
Cloudflare edge, DNS, Workers, R2
OVH k3s: app, data, platform
GCP secrets, OAuth, Places
GitHub CI, GHCR
Compute on OVH, everything public-facing and every blob on Cloudflare, identity and secrets on GCP, code and images on GitHub.
Rule of thumb for new infrastructure: anything that runs goes in the cluster; anything stored as an object goes in R2; secrets go in GCP Secret Manager.