authentik 2023.3.0 → 2023.4.0

2 versions, 1 with breaking changes, 1 required stop

Required stops

2023.3.1
Latest 2023.3.x release.
Upgrade sequence: Upgrades must follow the sequence of major releases; do not skip directly from an older major version to the most recent version.

Always upgrade to the latest minor version (.x) within each major.minor version before upgrading to the next major version. For example, if you're currently running 2025.2.1, upgrade in the following order:
1. Upgrade to the latest 2025.2.x.
2. Then to the latest 2025.4.x.
3. Finally to the latest 2025.6.x.
Outposts: The version of the authentik server and all authentik outposts must match. Ensure that all outposts are upgraded at the same time as the core authentik instance.
Source: https://docs.goauthentik.io/install-config/upgrade/#important-considerations (checked 2026-09-28)

Version by version, oldest first

2023.3.1 2023-03-16

Required stop

See required stops, above

Full release notes for 2023.3.1

2023.4.0 2023-04-14

Breaking

(Kubernetes only) Changes to RBAC objects created by helm

In previous versions, the helm chart would create a ClusterRole and ClusterRoleBinding if the service account creation was enabled. This was done to allow the deployment of outposts in any namespace in kubernetes. As this conflicted with multiple authentik installs per cluster, and was often not used, the new helm chart changes these resources to a Role and RoleBinding, which give authentik access to deploy in the same namespace.

To keep the old behavior, you can install the authentik-remote-cluster chart, which deploys the same RBAC into any other namespace or cluster.

From docs.goauthentik.io/releases/2023.4#breaking-changes

Full release notes for 2023.4.0

Release notes from github.com/goauthentik/authentik/releases, and the release notes on docs.goauthentik.io, checked 17 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. authentik publishes one release-notes page per YYYY.M release on docs.goauthentik.io. Its “Breaking changes” section is quoted whole as “Breaking” on the first release of that line (YYYY.M.0; 2022.1 to 2022.8 started at YYYY.M.1), its “Deprecations” section as “Note”, and the opening paragraph of its “Upgrading” section as “Note” unless it only says “This release does not introduce any new requirements”. Fixes in patch releases (“Fixed in …”) are not quoted, and neither are GitHub release notes (lists of merged pull requests). Versions are covered from 2022.1.0. Required stops: the latest patch release of every YYYY.M line on the way, per the upgrade documentation.