Skip to content
SHC Docs

Architecture

Layers 0 to 11. Layer map.

How the running system is put together. Coding bar: ../contributing/. Flat reference: ../reference/.

A layer is a documentation map, not a Go package and not a module list. One subject sits in one layer. The count is 0 to 11. Layer stack.

The host address the tunnels dial. Layer page.

mesh0, the node plane. Layer page.

The rqlite store and the leader. Layer page.

Jobs, schedules, and the event bus. Layer page.

Clusterfs, the node lease, labels and constraints, and pressure. No owner, no HUD page. Layer page.

Tenants, the vault, connections, catalogue apps, and config. Layer page.

The deployment is the running unit. A service has one virtual IP. Layer page.

One render, then one of four runtimes. Layer page.

The node materialises clusterfs and starts from the stored spec. Layer page.

shc0, container traffic. Layer page.

Publish, DNS, and the ingress files in clusterfs. Layer page.

Install, update, failover delivery, and relocate. Layer page.