Skip to content

Applications

Workloads that serve Tomoda traffic. Lives in k8s/apps/<name>/ as a Kustomize base plus per-environment overlays (dev, prod). The dev and prod Argo CD Applications point at the overlay path for their tier and reconcile the rendered Kustomize output into the cluster.

The pattern is the same in every case:

  • Base: environment-neutral manifests (Deployments, Services, Ingress, NetworkPolicies). Image refs point at GHCR (ghcr.io/tomoda-labs/*); overlays set the tag.
  • Overlay: namespace assignment, ExternalSecret pulls from GCP SM, ConfigMap with the env-specific DSNs, image tags, ingress hostnames, and any production-only resources (PDBs, HPAs).
  • Argo CD Application: points at the overlay directory. See Argo CD.

Tenant-scoped only

This section covers tenant workloads (Tomoda), plus Xavia OTA. Platform-tier services that aren't tenant code (Photon, oauth2-proxy, Traefik, etc.) live under Platform services.

  • Tomoda


    The product: Go backend (tomoda-api for HTTP + WS, tomoda-async for worker + scheduler) and Expo/React frontend. Kustomize base under k8s/apps/tomoda/, deployed into tomoda-dev and tomoda-prod.

  • Tomoda WS Pool Split


    Planned split of the WebSocket pool out of tomoda-api so HTTP and WS pods scale independently: trigger criteria, manifest sketch, migration sequence.

  • Xavia OTA


    Self-hosted over-the-air update servers for the mobile app (ota-dev, ota), bundles in R2.