Integrated outpost problem with latest helm chart #9005
Unanswered
joshuarestivo
asked this question in
Q&A
Replies: 1 comment
-
For posterity, what I'd been overlooking was creation of the local outpost integration (System -> Outpost Integrations). After creating that, modify the embedded outpost (Applications -> Outposts) to use it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to deploy a new authentik instance using the refactored helm chart (2024.2.2). I can get authentik deployed but there's no service created for the integrated outpost (eg., on port 9000/tcp). When I'd previously deployed authentik, using the 1.x chart, I don't recall having this issue. Is there something that needs to be done now to activate the listener?
Am I misremembering things? Does the embedded listener not get its own service exposed? Ultimately, I need to deploy the remote-cluster chart to wire up a remote cluster. I thought that I could just expose an ingress for the embedded listener and point everything back to it but, perhaps I'm going about this wrong. The documentation doesn't seem terribly clear on the details of the remote cluster architecture.
Beta Was this translation helpful? Give feedback.
All reactions