Deployment (Vultr / Kubernetes)
Per-tenant deployment on Kubernetes on Vultr, one namespace per tenant, from a single templated pipeline.
Topology per tenant
Each tenant namespace gets its own Postgres, Mongo, Redis, and bucket (managed services or in-cluster operators), plus its own secrets.
Templated deploy
- Helm (or Kustomize) chart parameterized by the Tenant Config Contract:
# values-utlsolar.yamltenantId: utlsolardomain: utlsolar.comimage: { tag: "1.4.0" }locales: [en-IN, hi-IN, ta-IN]featureFlags: { amc: true, loyalty: true, amazonChannel: true }secretsRef: utlsolar-secretsbucket: utlsolar-assets
- New tenant = new values file + secret + DNS. See Onboarding Runbook.
Images & releases
- One set of immutable images per release, shared across tenants.
- Release =
image tag + per-tenant values. Dev/prod parity via config only (12-factor).
Networking
- Ingress per tenant domain → Gateway/BFF.
- CDN in front of storefront + assets; WAF rules.
- Internal service-to-service over cluster network; egress allow-list for external APIs (SSRF control).
Data & backups
- Per-tenant backup schedules for Postgres + Mongo.
- Object-storage versioning for assets.
- Migration jobs run as one-off tasks from the release image (Medusa CLI for PG; versioned scripts for Mongo).
Scaling
- HPA per service; BullMQ worker pools scale independently.
- Storefront stateless + ISR + CDN absorbs read spikes.
- Noisy/large tenants isolated by namespace; can be moved to a dedicated node pool.
Secrets
- k8s Secrets / Vault per tenant; never in the Mongo config doc.
- Rotation runbook for gateway/courier/marketplace/webhook secrets.
Environments
dev→staging→prod, same charts, different values/secrets.- Preview environments per PR for web (optional) feeding Lighthouse/e2e.
Open questions
- Managed vs in-cluster Postgres/Mongo on Vultr (managed preferred for backups/HA).
- GitOps (Argo CD/Flux) for tenant rollouts — recommended.