Skip to content

Commit 63c5ab2

Browse files
committed
docs(dha): collapse to KEDA — query the metric, drop the controller and CRD
Address @lllamnyp's review: the read-replica metric need not be emitted per-pod — an aggregate value Σ+target with an AverageValue target makes stock HPA compute 1+ceil(Σ/target), so one PromQL query the chart authors replaces the per-pod encoding entirely. With the query in hand the guard controller and DatabaseScalingPolicy CRD dissolve: the chart renders a KEDA ScaledObject; KEDA queries vmselect and manages the HPA on the engine scale subresource. Brakes become static — quorum floor via minReplicaCount template arithmetic, scale-down pacing via a behavior literal, lag brake via a query-side clamp with hysteresis, dry-run by not rendering the object. Flux owns the ScaledObject declaratively, so no runtime writer of its spec exists. - §1: single-value Σ+target metric with worked arithmetic and Σ=0→1 note - §4: metric backend collapsed to the KEDA choice (prometheus-adapter and kube-metrics-adapter weighed) - §5: autoscaling values block + cozy-lib helper replace the controller/CRD - rollback made count-preserving (disable must not shrink a live cluster) - honest note: no active rollback of a stuck scale-up (pending+alert instead) - Alternatives: correct the External-metric entry; add rev3 guard+CRD as rejected; net-new surface rounds down to a helper, a values block, a query Signed-off-by: Alexey Artamonov <[email protected]>
1 parent 50dea51 commit 63c5ab2

1 file changed

Lines changed: 97 additions & 93 deletions

File tree

  • design-proposals/database-horizontal-autoscaling

0 commit comments

Comments
 (0)