website/docs: next release notes: add upgrade instructions for postgres to 16

[4d62]

Details

Provides documentation to upgrade authentik-postgresql to PG v16

closes #9628

---

Checklist

• Local tests pass (ak test authentik/)
• The code has been formatted (make lint-fix)

If an API change has been made

• The API schema has been updated (make gen-build)

If changes to the frontend have been made

• The code has been formatted (make web)

If applicable

• The documentation has been updated
• The documentation has been formatted (make website)

[netlify]

✅ Deploy Preview for authentik-storybook canceled.

Name	Link
🔨 Latest commit	3208e66
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-storybook/deploys/6654c0661cc7d90008376512

[netlify]

❌ Deploy Preview for authentik-docs failed.

Name	Link
🔨 Latest commit	69f9099
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-docs/deploys/6654b16cf2eaf80009948b49

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.64%. Comparing base (fd66be9) to head (3208e66).
Report is 57 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9727   +/-   ##
=======================================
  Coverage   92.64%   92.64%           
=======================================
  Files         710      710           
  Lines       34706    34745   +39     
=======================================
+ Hits        32152    32189   +37     
- Misses       2554     2556    +2     

Flag	Coverage Δ
e2e	49.66% <ø> (-0.01%)	⬇️
integration	25.50% <ø> (-0.02%)	⬇️
unit	90.09% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jehy]

Great PR! Just several hours ago I independently upgraded to postgres 16, there were no problems and it seems like authentik is working much faster.

[4d62]

Great PR! Just several hours ago I independently upgraded to postgres 16, there were no problems and it seems like authentik is working much faster.

Thanks! Out of curiosity, did you update with an existing database or did you recreate it? I'm currently facing the error psycopg.errors.DuplicateTable: relation "authentik_events_event" already exists and i'm looking for ways to make the upgrade easier. From wha I saw, it's impossible (unless i only saw the errors and not the success) to restore database from upgrade_backup_12.sql without purging it first due to already existing table errors.

[4d62]

also for project maintainers @BeryJu / @rissson, where should I put the markdown file once completed?

[rissson]

We'll probably include this in the release notes, so website/docs/releases/2024/next.md, which you can create from the template.

[rissson]

Great PR! Just several hours ago I independently upgraded to postgres 16, there were no problems and it seems like authentik is working much faster.

Yeah we've been testing 16 in CI pretty much since in came out, no issue. Interesting that it seems to be faster though!

[4d62]

Ok. thanks for the quick response. Regarding my issue, do you have any other suggestions or would you do it differently?

[rissson]

Great PR! Just several hours ago I independently upgraded to postgres 16, there were no problems and it seems like authentik is working much faster.

Thanks! Did you update with an existing database or did you recreate it? I'm currently facing the error psycopg.errors.DuplicateTable: relation "authentik_events_event" already exists and i'm looking for ways to make the upgrade easier. From wha I saw, it's impossible (unless i only saw the errors and not the success) to restore database from upgrade_backup_12.sql without purging it first due to already existing table errors.

You shouldn't need to re-create a database, restoring your dump file should be enough. pg_dump has arguments to delete objects if they already exist (-c, -C). The tables probably got re-created because authentik was running and thus executed its migrations as if it was a new install. As such, it should be shut down during the whole operation. The best way would be to cut off connections to postgresql completely, so network: none (don't remember the exact syntax) for a docker-compose installation, and firewalling for a standard postgres install.

[4d62]

I'll try that soon. Thanks!

[4d62]

Regarding K8s, someone would have to write the documentation as I don't really have any experience with it

[rissson]

Regarding K8s, someone would have to write the documentation as I don't really have any experience with it

We distribute postgres 15 with the helm chart, so we won't be upgrading that one soon.

[4d62]

@rissson I think this is ready for first review

[4d62]

Great info and steps to have, thanks @4d62ext !

No problem and thanks for the quick review.

[rissson]

@BeryJu something like this? tried adding headers like the example you provided

[rissson]

I'm so sorry, I misscliked.

something like this? tried adding headers like the example you provided

Yes!

[4d62]

my bad, tried renaming branch on my fork

[tanberry]

Thanks again @4d62ext !

[4d62]

Thanks again @4d62ext !

no problem!