Skip to content
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

Closed
samip5 opened this issue Oct 28, 2023 · 5 comments · Fixed by #230
Closed

FR: Allow at least two ingresses to be created from chart #209

samip5 opened this issue Oct 28, 2023 · 5 comments · Fixed by #230
Assignees

Comments

@samip5
Copy link

samip5 commented Oct 28, 2023

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..)

@rissson
Copy link
Member

rissson commented Nov 21, 2023

I'll probably add an extraResources value with 2024.1 which will allow that kind of use cases.

@rissson rissson self-assigned this Nov 21, 2023
@samip5
Copy link
Author

samip5 commented Feb 21, 2024

@rissson I don't really see how #230 would help, as I also need the outpost to generate two without having manually done it?

@rissson
Copy link
Member

rissson commented Feb 22, 2024

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.

@samip5
Copy link
Author

samip5 commented Feb 22, 2024

additional ingress manually anyway,

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.

@rissson
Copy link
Member

rissson commented Feb 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants