viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

t3-afk: scale to 0 — park the in-cluster T3 AFK executor (no current plans)
All checks were successful
ci/woodpecker/push/default Pipeline was successful
Details

Browse source 
Viktor has no near-term plans to use the autonomous AFK pipeline's in-cluster T3
cockpit/executor, so stop its pod to free node resources while keeping it
trivially revivable. Only the deployment replica count changes (1 -> 0); the SSD
PVC (state.sqlite + repo checkouts), Service, Ingress, and ExternalSecret are all
left in place — reviving is just setting replicas back to 1 and applying.

Already applied live via scripts/tg (PG state now 0 replicas, pod terminated);
this commit syncs git so drift-detection / the next apply won't re-scale it up.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-06-17 18:55:35 +00:00
parent b931d9fb20
commit aac7121ccc
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

6
stacks/t3-afk/main.tf
View file

@ -151,7 +151,11 @@ resource "kubernetes_deployment" "t3_afk" {
}
spec {
replicas = 1
# PARKED 2026-06-15: scaled to 0 — no current plans to run the AFK executor.
# Everything else is preserved (the SSD PVC with state.sqlite + repo
# checkouts, the Service, Ingress, and ExternalSecret), so reviving the
# in-cluster T3 cockpit is just flipping this back to 1 and applying.
replicas = 0
# Single-writer state.sqlite — never run two pods against the same base dir.
strategy {
type = "Recreate"