Ingress port mapping

[DaniTulp]

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:

service:
   port: {number}

This doesn't seem to be in the values.yaml. I do see this service.ports field so maybe that should be used instead?

[difabion]

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.

[DaniTulp]

Yeah that makes sense. As the readme also states WIP + using something that's undocumented is probably not the safest thing to do ;).
Thought I'd at least mention it in case someone else hits it as well. For my use case just defining the port as shown above works perfectly fine.

[difabion]

Revisiting this this week, bear with me.

[DaniTulp]

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.

[tbnguyen1407]

Hello, any progress on this issue? Currently .Values.service.port still needs to be manually added for ingress to be valid.