eliott/authentik
1
0
Fork 0
mirror of https://github.com/goauthentik/authentik synced 2026-05-05 06:32:15 +02:00
Code Issues Packages Projects Releases Wiki Activity

website/docs: update outpost upgrade doc (#17433)

Browse Source 
* Updated wording and screenshots

* Optimised images with calibre/image-actions

* Optimised images with calibre/image-actions

* Apply suggestions

---------

Co-authored-by: authentik-automation[bot] <135050075+authentik-automation[bot]@users.noreply.github.com>
This commit is contained in:
Dewi Roberts
2025-10-17 14:20:36 +01:00
committed by GitHub
parent 1f886e8848
commit 6c7fdf7113
4 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
website/docs/add-secure-apps/outposts/upgrading.md
View File

@@ -2,10 +2,14 @@
title: Upgrading an Outpost
---
In the Outpost Overview list, you'll see if any deployed outposts are out of date.
Outposts deployed using the [Docker](./integrations/docker.md) or [Kubernetes](./integrations/kubernetes.md) integrations are managed by authentik and are upgraded automatically. Outposts deployed manually via [Docker](./manual-deploy-docker-compose.md) or [Kubernetes](./manual-deploy-kubernetes.md) must be upgraded by updating the outpost's image tag to the new version.
![](./upgrading_outdated.png)
To check if any outposts are out-of-date, navigate to **Applications** > **Outposts** and look for a message in the **Health and Version** column.
To upgrade the Outpost to the latest version, simply adjust the docker tag of the outpost to the new version.
A red warning message will be shown on any outposts running outdated versions:
Since the configuration is managed by authentik, that's all you have to do.
![](./outpost-upgrade.png)
An up-to-date outpost will show a green message indicating the last successful connection with authentik:
![](./outpost-upgrade2.png)