feat(edge): k3s edge-worker + evolvable topology — Giant Swarm, reversed - #36
Merged
Conversation
The user's model: Giant Swarm runs a cloud management cluster that provisions workload clusters
top-down; we REVERSE it — the sovereign edge agent-machine (lightweight single-master k3s) registers
UP into a cloud pool as a worker, the twin a rendezvous not a master. And the topology is EVOLVABLE:
the same workload climbs k3s-edge -> k3s-server -> k8s-cloud; it shouldn't matter which rung.
compute_plane: `k3s-edge` is now a first-class backend — trusted, single-master, residency:edge
(the right-sized weight for an ephemeral dev node, not a lesser k8s). Sensitive workloads may run on
the sovereign edge.
tools/edge_worker.py:
- register_worker: the agent-machine joins a cloud pool as a worker; emits a mesh heartbeat so its
CPU is real placeable capacity, and advertises its local TopoLVM flash as a shared cluster mount
(compute AND storage into the pool).
- shared_storage_mount: the local TopoLVM inception mount, cluster-accessible via a container mount.
- evolve: migrate a workload across the ladder; state follows via the TopoLVM inception mount; no
rung is special.
docs/EDGE_WORKER.md articulates the reversed-Giant-Swarm model + why it beats both (sovereign edge
AND federate-up). Tests: +5 = 182 tools tests green. compute-plane CapD linked.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Giant Swarm reversed — they run a cloud management cluster that provisions workload clusters top-down (k8s-on-k8s); we invert it: the sovereign edge agent-machine (lightweight single-master k3s) registers up into a cloud pool as a worker; the twin is a rendezvous, not a master. And the topology is evolvable — the same workload climbs
k3s-edge → k3s-server → k8s-cloud; it shouldn't matter which rung.compute_plane:k3s-edgeis a first-class trusted, single-master backend (the right weight for an ephemeral dev node,residency: edge).edge_worker.register_worker: the box joins a cloud pool as a worker — emits a mesh heartbeat (its CPU becomes placeable capacity) and shares its local TopoLVM flash as a cluster mount (compute and storage into the pool).edge_worker.evolve: migrate a workload across the ladder; state follows via the TopoLVM inception mount.docs/EDGE_WORKER.md— why this beats both models (sovereign edge and federate-up). 182 tools tests green (+5).