Add the in-memory lease store: least-loaded selection, cooldowns, TTL retention
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -1,10 +1,12 @@
|
||||
# Architecture
|
||||
|
||||
> **Status:** the operator is built through Step 5 (health engine) of
|
||||
> **Status:** the operator is built through Step 6 (lease store) of
|
||||
> [docs/plans/2026-08-07-1747-proxy-operator.md](plans/2026-08-07-1747-proxy-operator.md).
|
||||
> This document currently covers the event/reconcile flow; the components
|
||||
> table and the Decisions section arrive with Step 10, and the diagrams
|
||||
> below grow as the lease store, discovery API, and orphan GC land.
|
||||
> table and the Decisions section arrive with Step 10. The lease store
|
||||
> (`internal/lease/`) is HTTP-driven, not cluster-event-driven, so its
|
||||
> diagram lands together with the discovery API in Step 7; the orphan-GC
|
||||
> flow lands with Step 9.
|
||||
|
||||
## Event flow: cluster events → reconciler functions
|
||||
|
||||
|
||||
Reference in New Issue
Block a user