-
Notifications
You must be signed in to change notification settings - Fork 23
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
Ingress port mapping #25
Comments
Admittedly, the ingress templating is not well-tested, and is mostly an artifact of the helm initialization logic for new projects. I'll get you an answer on this sometime over the weekend. |
Yeah that makes sense. As the readme also states WIP + using something that's undocumented is probably not the safest thing to do ;). |
Revisiting this this week, bear with me. |
No worries at all, due to the needs/opinions of the organisation I work for which (imo) don't directly align with what should be provided here (some quite specific options in terms of Azure for example). I've created our own helm chart (using this as reference of course 😉) that has those opinions baked in. |
Hello, any progress on this issue? Currently |
When messing around with the ingress I think I found an issue with the way it's setup. At least it's not documented. When defining the ingress it uses the following value:
This doesn't seem to be in the
values.yaml
. I do see thisservice.ports
field so maybe that should be used instead?The text was updated successfully, but these errors were encountered: