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
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:
@@ -1,5 +1,18 @@
|
||||
# Project status and next steps
|
||||
|
||||
## Explicit DEV worker placement - 2026-10-19
|
||||
|
||||
[ADR-0170](adr/0170-dev-worker-placement.md) implements the maintainer's worker
|
||||
placement requirement in the full DEV application and standalone region/store
|
||||
overlays. Required affinity excludes both current and legacy control-plane role
|
||||
labels. Existing store selectors, volumes, PostgreSQL endpoints and URLs remain.
|
||||
Rendered checks reject an unrestricted affinity alternative or `nodeName` bypass.
|
||||
|
||||
All 17 overlays render with zero policy failures; all 50 adversarial policy cases
|
||||
pass. [Evidence](engineering/M12_DEV_WORKER_PLACEMENT.md) distinguishes offline
|
||||
policy from actual running placement. Delivery uses Git Actions, Harbor, ArgoCD
|
||||
and Kubernetes. Target-host drills and the remaining M12 gates remain open.
|
||||
|
||||
## Retained-plan census and verified history - 2026-10-19
|
||||
|
||||
[ADR-0169](adr/0169-retained-plan-census-observations.md) adds raw owner-8 census
|
||||
|
||||
@@ -0,0 +1,43 @@
|
||||
# ADR-0170: Explicit DEV worker placement
|
||||
|
||||
## Status and scope
|
||||
|
||||
Accepted operational clarification, 2026-10-19, from the maintainer's requirement
|
||||
that DEV workloads run in `evolution-dev` and never on the control plane. Extends
|
||||
ADR-0076/0088 without changing biological rules, node labels, storage placement,
|
||||
database endpoints, credentials, URLs or World0 policy.
|
||||
|
||||
## Decision
|
||||
|
||||
Apply a reusable Kustomize component to the full DEV application and its
|
||||
standalone region/store overlays. Every current DEV Deployment and Job requires
|
||||
nodes without either `node-role.kubernetes.io/control-plane` or the older
|
||||
`node-role.kubernetes.io/master` label. Both exclusions belong to the same
|
||||
required selector term. Existing store selectors, volumes and resource settings
|
||||
remain. No control-plane toleration or node selector override is introduced.
|
||||
|
||||
The rendered deployment policy requires both exclusions in **every** required
|
||||
node-affinity term, since terms are alternatives. It also refuses explicit
|
||||
`nodeName`, which bypasses scheduler selection. Future DEV workload kinds must
|
||||
provide the same restriction before passing the policy. Shared bases, stage,
|
||||
monitoring and operator-only inventory examples keep their existing scope.
|
||||
|
||||
## Alternatives and consequences
|
||||
|
||||
Relying only on common control-plane taints is weaker than the explicit
|
||||
requirement: taints are external cluster configuration. Replacing the store
|
||||
selector with a particular hostname would couple the application to an unknown
|
||||
node and could strand its node-local volume. Required negative role affinity
|
||||
preserves current placement constraints while preventing scheduling onto a
|
||||
correctly role-labelled control plane.
|
||||
|
||||
If no eligible worker owns the existing volume, pods remain Pending. Do not
|
||||
relax the rule or move retained storage merely to obtain readiness. Cluster role
|
||||
labels remain an infrastructure responsibility; offline rendering cannot verify
|
||||
their truth or prove a running pod's placement.
|
||||
|
||||
Delivery uses the existing Git Actions -> Harbor -> ArgoCD -> Kubernetes flow.
|
||||
Qualify effective rendered objects and adversarial patches (removed affinity,
|
||||
missing legacy-role exclusion, unrestricted OR term and direct `nodeName`).
|
||||
Record actual rollout, placement and target-host measurements separately. No
|
||||
direct deployment, live reachability or M12 completion is inferred from a push.
|
||||
@@ -1,5 +1,7 @@
|
||||
# Architecture decision records
|
||||
|
||||
- [ADR-0170: Explicit DEV worker placement](0170-dev-worker-placement.md) - required control-plane/master exclusion for DEV workloads in full and standalone overlays, with rendered-policy regression checks; no live-placement claim.
|
||||
|
||||
- [ADR-0169: Retained-plan census observations](0169-retained-plan-census-observations.md) - raw owner-8 projection 2 separates expressed resident stock from living offspring-plan references and dead-plan history; verified history and registered capture retain exact boundaries.
|
||||
|
||||
- [ADR-0168: Durable raw retained-plan admission](0168-durable-retained-plan-admission.md) - schema 55, explicit raw bundle-11 -> 12 fenced upgrades and trace-4 mutation/birth publication with exact recovery; no automatic opening or population admission.
|
||||
|
||||
@@ -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.
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user