Containers, K8s, microVMs
One DaemonSet. One mesh. Every pod.
A Helm chart deploys one beacons-agent per node as a DaemonSet. Workloads inside the cluster join the mesh through the agent's loopback bridge. Want a sidecar-per-pod model instead? There's a chart for that too.
What you get.
- Helm chart published at oci://ghcr.io/l1feai/beacons-chart
- DaemonSet · sidecar · single-pod admin agent — three modes
- mTLS between agent and coordinator; no shared cluster secret
- Hives flights auto-enroll on launch via the WASM target
- Firecracker microVMs run the standard Linux daemon inside
helm — install beacons DaemonSet
helm install beacons oci://ghcr.io/l1feai/beacons-chart \ --set fleet=did:oas:acme:fleet:prod \ --set capabilityFromSecret=arsenal-token → DaemonSet beacons created on 24 nodes → pods join the mesh through node-local agent
Supported platforms
The full list.
| Platform | Tier | Implementation | Channel |
|---|---|---|---|
| OCI container peer | T7 | beacons-core Linux binary in a container | Docker Hub · GHCR |
| Kubernetes DaemonSet | T7 | Helm chart, one daemon per node | Helm registry |
| Kubernetes pod sidecar | T7 | Helm chart, one sidecar per pod | Helm registry |
| Hives flight (WASM) | T6 | WASM/WASI build inside Hives Wasmtime | Hives registry |
| Firecracker microVMs | T1 | Standard Linux binary inside the microVM | Vendor channels |
| Kata containers | T1 | Same as Firecracker | Vendor channels |