Context
kobe has auto-delete (lease TTL) and coarse pool scale_down_after, but no per-cluster sleep/resume. Scale-to-zero control planes with wake-on-access are a proven cost pattern worth adapting. The connect-proxy already intercepts all client traffic, so it can drive wake-on-access.
Proposal
- Pause/Resume via annotation pattern (truth on the CR, operator-driven, survives a degraded control plane).
- Auto-sleep schedule + wake-on-connect through the connect-proxy; publish the idle-lease cost model alongside.
Acceptance
An idle lease sleeps (control plane scaled to 0) and resumes on access; schedule configurable per pool.
Context
kobe has auto-delete (lease TTL) and coarse pool
scale_down_after, but no per-cluster sleep/resume. Scale-to-zero control planes with wake-on-access are a proven cost pattern worth adapting. The connect-proxy already intercepts all client traffic, so it can drive wake-on-access.Proposal
Acceptance
An idle lease sleeps (control plane scaled to 0) and resumes on access; schedule configurable per pool.