app.ingress.tls.enabled: ingress' $servicePort should not depend on it but on `kong.proxy.tls.enabled`

[zerkms]

What happened?

If you set kong.proxy.tls.enabled=false so that traffic between kubernetes cluster-wide ingress and kong was not unnecessary https'ed, then it's impossible to generate a kind: Ingress object anymore.

Why:

{{- $servicePort := (ternary $.Values.kong.proxy.tls.servicePort $.Values.kong.proxy.http.servicePort $.Values.app.ingress.tls.enabled) }}

This is how the service port for kong is evaluated. And given I DO want tls for my public host - I should have app.ingress.tls.enabled=true, yet it configures the ingress as

          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: kong-proxy
                port:
                  number: 443

Instead $servicePort should depend on kong.proxy.tls.enabled

What did you expect to happen?

It should be possible to generate Ingress

How can we reproduce it (as minimally and precisely as possible)?

Deploy with

app:
  ingress:
    tls:
      enabled: true

kong:
  proxy:
    http:
      enabled: true
    tls:
      enabled: false

Anything else we need to know?

No response

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

chart v7.14.0

Kubernetes version

1.33.x

Dev environment

No response