etcd, Consul, and Kubernetes Lease
Latest stable Based on Leader release 0.4.0
Use control-plane-native ownership where the control plane is already the system of record.
The preview etcd backend uses the v3 Lock service and leases, with single and group variants. Lease keepalive and client session health are central; test compaction, reconnect, and server quorum loss in the target topology.
Consul
Section titled “Consul”The preview Consul backend combines Sessions and KV. Session renewal defines liveness, and single/group blocking and suspend paths are available. Treat session invalidation and network partitions as ownership-loss events.
Kubernetes
Section titled “Kubernetes”The preview Kubernetes backend writes coordination.k8s.io/v1 Lease resources. It is appropriate for controllers and operators already governed by the cluster API. API-server availability, RBAC, namespace, lease duration, and pod termination grace all enter the operational contract.
Boundary
Section titled “Boundary”Do not add a control plane only for a scheduled job. Choose these modules when the control plane is already authoritative and its availability objective is acceptable for the work.