Allow to select service port for ingress

[piotrwielgolaski-tomtom]

I would like to expose kong-admin as ingress, but it force to use tls port in ingress. https://github.com/Kong/charts/blob/main/charts/kong/templates/_helpers.tpl#L421

I need tls for controller in gateway mode, but I would prefer to use http for kong-manager and expose it ingress. Prefer to not to make ssl passthrough as it is not easy with plain ingress resources.

[rainest]

Can you elaborate on your situation? Manager should be able to access the admin API over HTTPS fine.

[piotrwielgolaski-tomtom]

My case is like this, I use traefik as ingress to expose admin API, but it is up to traefik to terminate SSL and forward http to pod, with current setup, ingress need to be configured to passthrough ssl from client to pod, which is not trivial. To solve it for now, I was forced to disable ingress from kong chart and create one outside only because when tls is on, it force ingress to use tls port.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[bss-dmitry-shmakov]

using kong as part of default kubernetes-dashboard chart, and noticed that it's impossible to make it listen on http port instead of https, the https is chosen in variables even if values passed are 'tls.enabled: false' , the vars end up being tls mode (uses 8443 in KONG_PROXY_LISTEN and KONG_PORT_MAPS). so by default the tls cannot be disabled now in current version of the chart (without patching it over with kubectl after the fact). just my 2 cents, i hope it helps someone who ends up here from google (override these variables in kong deployment, and only after that it'll be possible to point your existing ingress that does tls termination, to the kong proxy on http port). should i file a bug report for it? (the conditional in helm template is wrong i think, that's why impossible to control it from values only, need to patch)