Reopen: Outpost Controller task (and thus respective pods) not starting when Authentik is started with helm chart (#9574)

[hamlet42]

Reopen of #9574 as I did not find a way to reopen this issue directly. The supplied fix did not change the behavior described.

I was not sure if the comment on the closed issue is noted. So my apologies if this is not right way to do that.

Additional info: I am using the default tenant. No other tenants have been created.

Regs Helmut

[authentik-automation[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[hamlet42]

Issue is still open, same behavior in 2024.6.0 and 2024.6.1

[hamlet42]

Issue also present in 2024.6.2

[hamlet42]

Issue still present in 2024.6.3

[hamlet42]

Issue still present also in 2024.6.4

[BeryJu]

@hamlet42 how are the outposts in authentik created? Every method of creating an outpost should trigger the same logic to run the tasks behind it.

[hamlet42]

@BeryJu in the web interface of authentic as akadmin. The outposts have been created a year + ago. Once the behavior above was occurring, I deleted them and created them anew, also in the web interface. Nothing fancy about these outposts and their definitions from my understanding.

[BeryJu]

I'm still not quite sure I understand what the issue is, I'm assuming when authentik is upgraded the outposts aren't upgraded on startup?

[hamlet42]

I originally started to unload the outpost pods when I uninstall the authentik helm chart seeing that the pods got not updated when there are newer ones (or at least was deducing it as an issue at this time, it was many versions ago). And I wanted nothing to remain when I uninstall a chart. Just for sake of clarity.

Hope this helps on understanding the intention. And agreed, it is maybe not necessary :-)

I checked again on 2024.8.1 and the issue is still existing.

[hamlet42]

I checked again on 2024.8.2 and the issue is still there.