Files
aevolution/docs/engineering/M12_DEV_WORKER_PLACEMENT.md
T
dingo fad79973e2
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m24s
Foundation / postgres-tools (push) Successful in 6s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 6s
fix(deploy): constrain DEV workloads to worker nodes
2026-10-19 15:08:00 -04:00

2.1 KiB

DEV worker placement qualification

2026-10-19, ADR-0170. The maintainer confirmed Git Actions -> Harbor -> ArgoCD -> Kubernetes delivery from deploy/, with DEV workloads in evolution-dev, on workers, and the existing PostgreSQL server/network/URLs. This segment makes the placement requirement explicit in the delivered manifests; it does not replace the configured pipeline.

The full DEV overlay and standalone region/store overlays apply the same component. All current DEV Deployments and Jobs exclude nodes carrying either standard control-plane role label. Existing store selectors and volume claims remain, so a missing eligible worker leaves the workload unscheduled rather than silently using the control plane. The component does not allocate/move storage, change database endpoints or grant credentials.

Executed locally with the repository-pinned Kustomize v5.8.1:

  • Rendered deployment policy: 75 objects in 75 files, 138 rendered objects in 17 overlays, zero failures.
  • Deployment policy self-test: 50 cases, zero failures. The four added cases remove required affinity, remove the older master-role exclusion, append an unrestricted OR term and set direct nodeName. All are refused. Existing namespace, route, window, port and NetworkPolicy regressions remain.
  • The route self-test helper now preserves existing components when enabling the route, rather than appending a duplicate YAML key that drops other rules.

The policy checks effective rendered objects, not only patch text. Every required selector alternative must exclude both roles. It also refuses a nodeName bypass for every DEV workload kind. Future workload kinds need equivalent affinity before entering the delivery path; no new placeholder workload is added.

This is offline policy evidence. Actual node role labels, running pod placement, image rollout, readiness, multi-host failures and M12 target-host performance need results from the delivered environment. A Git push or local policy pass alone cannot supply those results. No direct cluster operation or World0 deployment/reset/pruning occurred.