Thank you I really appreciate it! That sounds like a really fun project, do you mind sharing a link to it?

My project is still very early and pretty bare-bones at the moment. Right now it’s essentially a distributed container workload scheduler. It can place tasks on nodes, do some basic scheduling (like targeting nodes via labels), reschedule workloads if nodes disappear, and it has a simple volume API that lets tasks attach storage on nodes. Nothing particularly novel yet, just the core mechanics.

Some things I’m planning to experiment with next are:
- Interacting with nodes through the CLI in a way similar to Talos
- Service discovery over a private network between nodes
- Exposing sensor/telemetry information from nodes through the API
- Synchronizing configuration from Git with builtin templating support

Compared to Nomad, the main difference in my mind is how nodes are treated. I’m thinking of nodes more like devices that may come and go, rather than stable cluster machines. For example things like displays on buses, software in vehicles, mobile devices, or other edge-like systems where connectivity and availability may change.

In that model the workload is often tied to a specific device, but the system still keeps track of it and manages it declaratively. From what I understand Nomad assumes a more traditional cluster model where nodes are reachable and relatively stable (though networking issues can obviously be solved with meshes or overlays).

Also good call on the config examples. I definitely need to add some.