Separate RedDwarf control plane from persistent remote workers #2
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/cluster-workers-20261001"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
RedDwarf WI-1: 01a0f6e0-dbd4-7051-b3e0-40ae5c21ad65
Adds
control-planeandworkermodes while preservingserveand all-in-oneagent. One API/database/scheduler owns cluster resources; each worker holds only local identity and persistent IPAM. Atomic node admission rejects duplicate identity/name, CIDR changes and overlapping pod/service networks. HTTP clients validate the origin/CA, use bounded requests, and workers retry transient registration/heartbeat outages. Remote assigned-pod reconciliation uses documented bounded polling.Validation at
74b7fcc19a: native oibldofgate workspace tests, binary build, formatting, strict all-targets Clippy, SMF validation, API/TLS process smoke and two independent worker processes all passed. Topology checks include concurrent overlapping registration, state-file double start, heartbeat, assigned-node filtering, worker restart/persistent identity and IPAM, control-plane outage/reconnect and deletion. Local tests/lint and topology smoke also passed.Mock runtime is an explicit native test mode without ZFS/zone/NAT mutations. This is transport proof; real zone images, owned forwarding, API authentication and CI/runner pilot remain separate plan milestones. No new binary target is added. Native SSH checks are not Anima CI: canonical CI is currently unconfigured.