Skip to content

ops(dev): pin backend to dev-pool, off spot (closes #678) #679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lilyshen0722 merged 1 commit into from
Jul 12, 2026
Merged

ops(dev): pin backend to dev-pool, off spot (closes #678) #679

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions k8s/helm/commonly/values-dev.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,15 +18,18 @@ backend:
repository: gcr.io/YOUR_GCP_PROJECT_ID/commonly-backend
tag: "20260417214615-r4"
pullPolicy: Always # Always pull in dev
# ADR-015: backend is stateless and tolerates a 30s reschedule on spot
# reclaim — socket.io reconnects automatically, mid-flight HTTP gets one
# 502. Keeps the larger always-on cost off the dev cluster.
# ADR-015 amendment (2026-07-12): the backend serves the user-facing API and
# is the one workload a spot reclamation must never interrupt. It requests
# only 200m/512Mi and fits in existing dev-pool headroom, so pinning it to the
# on-demand pool closes the abrupt-reclamation gap for ~$0 (cheaper than a 2nd
# replica, which would also stay on spot). Spot stays for restartable/batch
# workloads (agents, LiteLLM); the user-facing API + Redis belong on dev-pool.
nodeSelector:
workload-tier: spot
pool: dev
tolerations:
- key: "workload-tier"
- key: "pool"
operator: "Equal"
value: "spot"
value: "dev"
effect: "NoSchedule"
env:
nodeEnv: development
Expand Down
Loading