Alexey Artamonov 3a4bade677 docs(postgres): document the kind-wide scope of the client-side apply flip ...

The release.cozystack.io/helm-server-side-apply annotation moves every Postgres
HelmRelease to client-side apply, including releases that never enable
autoscaling. IvanHunters flagged that this platform-wide side effect was
unexplained and that non-autoscaled releases silently lose SSA drift
re-assertion (client-side diffs previous-vs-new render only, never live state;
driftDetection is configured nowhere in the repo).

Record why the scope is deliberate rather than narrowing it. helm-controller
v1.5.0 resolves an unset Upgrade.ServerSideApply through "auto" from the last
release's apply method, so gating client-side on "autoscaling active" would
force an SSA->client-side ownership handoff on the live spec.instances the
moment a tenant enables autoscaling - the exact live-field handoff the seed
design was chosen to avoid. Keeping the apply method stable for the kind's whole
lifecycle keeps enable/dry-run/transition/disable clean two-way merges with no
apply-method transition. The drift-re-assertion cost on never-autoscaled
releases is called out as an accepted trade-off, with a per-instance apply
strategy as the follow-up if it is ever needed.

Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>

2026-09-07 22:06:21 +03:00

..

config_test.go

feat(api): add per-app helm apply-strategy override annotation

2026-09-04 23:19:25 +03:00

config.go

docs(postgres): document the kind-wide scope of the client-side apply flip

2026-09-07 22:06:21 +03:00

waitstrategy_test.go

feat(api): typed waitStrategy/healthCheckExprs for kstatus readiness

2026-07-16 16:45:16 +05:00