You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using a Authentik instance with the helm chart under K3s.
When I start Authentik with the helm chart, the respective Outpost pods are not created automatically. Reasons seems to be that the respective system tasks (Outpost Controller) per Outpost are not starting automatically, only the one for the embedded outpost. The outposts are shown unhealthy in the dashboard overview page.
This worked for me until the 2023.x releases and stopped working, I think, with the 2024.x releases for me.
I created logs on DEBUG level and checked them but no errors that pointed me to the root cause.
To reproduce the behavior:
Bring authentik down with "helm uninstall authentik"
Delete outpost pods with kubectl scale --replicas=0 deployment/ak-outpost-xxx
Bring authentik up with "helm install authentik"
Workaround:
Only if I open the config of the outpost and click "Update" (not changing anything in the config), the respective system task "outpost_controller: xxx" is created as can be seen in the system tasks page and the respective outpost pod is created.
Can some confirm that change in the behavior? Or did I miss a setting that is now required and not set, eg. from the breaking changes coming with 2024.x?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am using a Authentik instance with the helm chart under K3s.
When I start Authentik with the helm chart, the respective Outpost pods are not created automatically. Reasons seems to be that the respective system tasks (Outpost Controller) per Outpost are not starting automatically, only the one for the embedded outpost. The outposts are shown unhealthy in the dashboard overview page.
This worked for me until the 2023.x releases and stopped working, I think, with the 2024.x releases for me.
I created logs on DEBUG level and checked them but no errors that pointed me to the root cause.
To reproduce the behavior:
Workaround:
Only if I open the config of the outpost and click "Update" (not changing anything in the config), the respective system task "outpost_controller: xxx" is created as can be seen in the system tasks page and the respective outpost pod is created.
Can some confirm that change in the behavior? Or did I miss a setting that is now required and not set, eg. from the breaking changes coming with 2024.x?
Any ideas or feedback appreciated.
Regs Helmut
Beta Was this translation helpful? Give feedback.
All reactions