geonode ingress targets wrong service port when TLS is configured

zalf-rdm / geonode-k8s

A Kubernetes helm chart for the geospacial webapplication Geonode

https://geonode-k8s.readthedocs.io/en/latest/

GNU General Public License v2.0

12 stars 7 forks source link

geonode ingress targets wrong service port when TLS is configured #38

Closed ridoo closed 1 year ago

ridoo commented 1 year ago

The geonode's ingress uses the .Values.geonode.ingress.externalPort to target the geonode nginx service. This is wrong as the service stays on port 80.

https://github.com/zalf-rdm/geonode-k8s/blob/d748731ee09d5bb310a9c49bcf2c59cd93eeabb7/deployment/geonode/templates/nginx/nginx-ingress.yaml#L29-L36

This results in an HTTP 503 error when ingress is configured to use TLS (port 443).

ridoo commented 1 year ago

already fixed https://github.com/zalf-rdm/geonode-k8s/pull/36