charts/authentik: move bundled PostgreSQL to the Debian 13 base - #523
Merged
Merged
Conversation
BeryJu
approved these changes
Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Changes the bundled PostgreSQL image default from
17.11-bookworm(Debian 12) to17.11-trixie(Debian 13). Same PostgreSQL version, same Docker Official image — only the base changes.Why
postgres:17.11-bookwormcurrently scans with 30 critical CVEs, and 28 of them are Debian 12 OS packages that Debian has markedwont-fixornot-fixed— they will not be patched in bookworm:Trixie ships substantially newer versions of each: perl 5.40.1, glibc 2.41, openssl 3.5.7, sqlite3 3.46.1.
One caveat in the interest of accuracy: libxml2 in trixie is
2.12.7+dfsg+really2.9.14, i.e. the same 2.9.14 upstream content, so CVE-2026-6653 is not addressed by this change.Consistency: this chart already ships Debian 13 in the same
values.yaml—volumePermissions.imageisdebian:13-slimsince #434. The database container is the last Debian 12 image in the chart.Renovate cannot propose this.
dockerversioning treats-bookwormas a compatibility suffix and only offers versions carrying the same suffix — the dependency dashboard (#357) lists the only available update for17.11-bookwormas18.6-bookworm. The base will stay on Debian 12 indefinitely unless changed by hand.Upgrade note — worth weighing
Moving bookworm to trixie changes glibc 2.36 to 2.41. PostgreSQL records the collation version of the libc it was initialised against, so existing clusters may log a collation version mismatch warning, and indexes on text columns should be
REINDEXed to be strictly correct.That makes this more than a cosmetic swap for existing deployments, and you may prefer to do it at a major-version boundary instead. Happy to redo this as
18.x-trixiealongside #402, or to add an upgrade note to the README — your call.I considered
17.11-alpine, which has a much smaller CVE surface, but rejected it: musl changes collation behaviour more than a glibc version bump does, which is a bigger ask of existing users.Testing
Only the default value changes;
ct installexercises a fresh install on the new base.Disclosure: this change was prepared with the help of an LLM (Claude Code). The CVE data comes from a Kubescape scan of a running cluster; the Debian package versions were verified against sources.debian.org. I reviewed and vetted the change before raising it.