-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Allow at least two ingresses to be created from chart #209
Comments
I'll probably add an |
So for outposts, as that's done by authentik, you'd still need to create the additional ingress manually anyway, which you can do with the changes from #230. |
Which should be supported from inside Authentik when configuring the outpost, which it's not so all changes to the domains need to be manually done. |
That is indeed not supported currently. You can work around this by creating a new notification rule and associate a policy to it. In that policy, you can write Python, so you can create/update/delete ingresses as needed. Here is a an example that does that but for providers instead of outposts, and pushes a secret to vault instead of working with ingresses. Otherwise, you can open a feature request here. |
I would love if it chart supported more than single ingress to be deployed as I need one external and one internal. :)
(I know I can do it outside the chart, but..)
The text was updated successfully, but these errors were encountered: