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.
0. Underlay
Section titled “0. Underlay”The host address the tunnels dial. Layer page.
1. Mesh
Section titled “1. Mesh”mesh0, the node plane. Layer page.
2. Core
Section titled “2. Core”The rqlite store and the leader. Layer page.
3. Work
Section titled “3. Work”Jobs, schedules, and the event bus. Layer page.
4. Primitives
Section titled “4. Primitives”Clusterfs, the node lease, labels and constraints, and pressure. No owner, no HUD page. Layer page.
5. Objects
Section titled “5. Objects”Tenants, the vault, connections, catalogue apps, and config. Layer page.
6. Services
Section titled “6. Services”The deployment is the running unit. A service has one virtual IP. Layer page.
7. Engine
Section titled “7. Engine”One render, then one of four runtimes. Layer page.
- Render once
- Docker
- Runtime support
- Shell
- Completion
- Communication patterns
- Cross-module interactions
- Import DAG
- Docker file operations
8. Node
Section titled “8. Node”The node materialises clusterfs and starts from the stored spec. Layer page.
9. Fabric
Section titled “9. Fabric”shc0, container traffic. Layer page.
10. Edge
Section titled “10. Edge”Publish, DNS, and the ingress files in clusterfs. Layer page.
- Networking
- DNS and HTTPS
- DNS provider sync
- DNS
- Forward
- SSO redirect coverage
- Authentication
- Launcher
- Identity and permission matrix
11. Lifecycle
Section titled “11. Lifecycle”Install, update, failover delivery, and relocate. Layer page.
- Host lifecycle
- Flows
- Install
- Update
- Failover
- Relocate
- Uninstall
- Backup and restore
- Deploy, restore, recover
- Clone
- Backup
- Export
- Retention