Upgrading directly the newest recipe version breaks Authentik #25

Open
opened 2026-03-20 03:18:32 +00:00 by featherbutt · 0 comments

I attempted to deploy the lastest version of the Authentik recipe from cfb8c021, and encountered the same issue outlined in https://github.com/goauthentik/authentik/issues/20634

Apparently, it is not possible to update authentik directly to the newest version: it must be upgraded to each intermediate version in sequence, as outlined at https://docs.goauthentik.io/install-config/upgrade/

Is it possible to guard against this pattern by detecting and prevent unsafe deployments like this, or otherwise display a warning? This seems like a very easy mistake to make.

I attempted to deploy the lastest version of the Authentik recipe from cfb8c021, and encountered the same issue outlined in https://github.com/goauthentik/authentik/issues/20634 Apparently, it is not possible to update authentik directly to the newest version: it must be upgraded to each intermediate version in sequence, as outlined at https://docs.goauthentik.io/install-config/upgrade/ Is it possible to guard against this pattern by detecting and prevent unsafe deployments like this, or otherwise display a warning? This seems like a very easy mistake to make.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/authentik#25
No description provided.