d5e04a2301
* *: remove backup Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * fix lint Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * website/docs: add docs Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * *: final cleanup Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * ci: use correct pyproject when migrating from stable Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * website/docs: fix broken docs Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>
1.4 KiB
1.4 KiB
| title | slug |
|---|---|
| Release 2022.2 | 2022.2 |
Breaking changes
Removal of integrated backup
The integrated backup functionality has been removed due to the following reasons:
- It caused a lot of issues during restore, with things breaking and difficult to restore backups
- Limited compatibility (only supported local and S3 backups)
- Most environments already have a solution for backups, so we feel that investing more time into making this feature better should be spent on more important things.
If you don't already have a standard backup solution for other applications, you can consider these replacements:
- https://github.com/kartoza/docker-pg-backup for docker-compose and
- https://devtron.ai/blog/creating-a-kubernetes-cron-job-to-backup-postgres-db/ or https://cwienczek.com/2020/06/simple-backup-of-postgres-database-in-kubernetes/ for Kubernetes
Upgrading
This release does not introduce any new requirements.
docker-compose
Download the docker-compose file for 2022.2 from here. Afterwards, simply run docker-compose up -d.
The previous backup directory will persist, and can still be used with other tools.
Kubernetes
Update your values to use the new images:
image:
repository: ghcr.io/goauthentik/server
tag: 2022.2.1
Backup-related settings can be removed but will not cause any errors either.