The release carried upgrade remediation with three retries and no strategy. The
Flux CRD is explicit: the strategy defaults to rollback, remediation runs between
each attempt, and the last failure is remediated as well whenever retries exceed
zero. A failing upgrade would therefore have rolled Helm back to the old version
up to four times, against a database Django had already migrated forward — the
migration inconsistency Authentik's own documentation warns about, triggered by
this line.
Here the way back is a database restore, not a version rollback, so an automatic
rollback cannot help and can only deepen the damage. It goes back to three once
the jump is done; outside a migration window the remediation is right.
Nothing else changes: the chart version, the values and the install remediation
are untouched.
Thore Cimbal
df6d291d81