Installed Authentik on Kubernetes (K3s v1.30.1) using Helm. Works fine for OAuth. I want ro use a separate outpost and created it using the example manifests (just replacing the __AUTHENTIK_XXXX__ values). It doesn't seem to work because the log of the Outpost Pod is flooded with:
level=error event="Failed to fetch outpost configuration, retrying in 3 seconds" error="403 Forbidden" logger=authentik.outpost.ak-api-controller
Since it seems to be an autehntication issue I wonder if it has to do with the'__AUTHENTIK_TOKEN__' value specified in the Secret. There is no 'token' value in the Authentik Helm chart values file, so I'm not sure what to put there and if it is related to the issue.
Version and Deployment:
authentik version: 2024.8.1]
Deployment: Helm
Platform K3s v1.30.1
Host OS: Debian 12.6
Additional context:
The manifests used (through Ansible):
When you create a managed proxy outpost in the Web UI it will show deployment info on the right, you click there and a window will pop up and from there you can copy the generate token for that outpost.
Installed Authentik on Kubernetes (K3s v1.30.1) using Helm. Works fine for OAuth. I want ro use a separate outpost and created it using the example manifests (just replacing the
__AUTHENTIK_XXXX__
values). It doesn't seem to work because the log of the Outpost Pod is flooded with:Since it seems to be an autehntication issue I wonder if it has to do with the'__AUTHENTIK_TOKEN__' value specified in the Secret. There is no 'token' value in the Authentik Helm chart values file, so I'm not sure what to put there and if it is related to the issue.
Version and Deployment:
Additional context: The manifests used (through Ansible):