fix(deploy): constrain DEV workloads to worker nodes
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

This commit is contained in:
dingo
2026-10-19 15:08:00 -04:00
parent dc7c0e1fa1
commit fad79973e2
14 changed files with 223 additions and 2 deletions
@@ -0,0 +1,36 @@
# DEV worker placement qualification
2026-10-19, [ADR-0170](../adr/0170-dev-worker-placement.md). 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.
+5
View File
@@ -36,6 +36,11 @@ on worker nodes, using the existing PostgreSQL server/network endpoints and
isolated test data. A successful local check or Git push alone is not evidence
that a target-host fault drill or deployed workload passed. Direct workstation
Kubernetes access is not a prerequisite for this delivery flow.
[ADR-0170](../adr/0170-dev-worker-placement.md) now enforces required worker
placement in full/standalone DEV overlays and rendered policy, including all
affinity alternatives and direct-node bypasses. Its
[50-case policy proof](M12_DEV_WORKER_PLACEMENT.md) does not establish actual
node labels, deployed placement, rollout success or target-host performance.
## Persistence boundary resolved by 12.3b
+31
View File
@@ -1,5 +1,36 @@
# Validation report
## 2026-10-19 - Explicit worker-only DEV scheduling
[ADR-0170](../adr/0170-dev-worker-placement.md) applies required negative
control-plane/master role affinity to current DEV Deployments and Jobs in the
full application and standalone region/store overlays. It preserves store
selectors, claims, requests and network/database endpoints. The rendered policy
checks every required selector alternative and refuses direct `nodeName`.
Executed locally with pinned Kustomize v5.8.1:
- Deployment policy: **75 objects in 75 files, 138 rendered objects in 17
overlays, zero failures**.
- Full policy self-test: **50 cases, zero failures**. Four new cases refuse
removed affinity, missing legacy master exclusion, an unrestricted OR term
and a direct node bypass. Existing route/window/network/namespace checks pass.
- Staged/working diff checks pass. No C++/biological rule or golden changes;
no further compiler/sanitizer rerun is warranted for these manifest/Python/docs
changes. The preceding census section records the full C++ validation.
The self-test route helper now preserves all existing components when enabling
the route, without duplicate YAML keys. Detailed scope is in
[the placement report](M12_DEV_WORKER_PLACEMENT.md).
Delivery remains Git Actions -> Harbor -> ArgoCD -> Kubernetes. Offline policy
does not verify actual cluster role labels, deployed placement, successful
image rollout, reachability, target-host costs or multi-host failures. No direct
cluster operation, new workload service or World0 operation occurred. These
checks do not complete M12's ecology, control/UI, actual-days or product gates.
The worker-placement push refreshes the DEV session window to
**2026-10-19 23:07:30 UTC**; live reachability still requires deployment evidence.
## 2026-10-19 - Retained-plan census projection 2 and committed observations
[ADR-0169](../adr/0169-retained-plan-census-observations.md) and the