fiberd

Overview ¶

Command fiberd verifies signed grants offline, mints fibers under them through a runtime, and serves the grant protocol (api/grant/v1) over gRPC. One process serves one home instance. fiberd itself is pkg/fiberd.

fiberd [flags]                      serve this home
fiberd run [flags] TEMPLATE [args]  try a template on this machine
fiberd healthz [flags]              ask a running fiberd for /healthz
fiberd readyz [flags]               ask a running fiberd for /readyz

-home picks the home fiberd runs in. standalone, the default, is a plain host. kubernetes is a grant Pod, whose identity the downward API fills through POD_NAME, POD_NAMESPACE and POD_UID. Homes are core and live under pkg/home. Control planes, such as the controller that creates grant Pods, are separate projects that pin this module.

healthz and readyz take the same flags, so -state names the admin socket. They need no Pod identity. A liveness probe can exec healthz, and a readiness probe that should see a drain can exec readyz, which also fails while fiberd drains.

Startup order is fixed: epoch++ -> reconcile -> open RPC. fiberd serves nothing until its view of the home is real.

The exit code is 0 for a clean stop, -h or -version, 2 for bad flags or usage, and 1 when fiberd or a probe fails.