Specifying a service's port name instead of number does not work

[lion7]

I just installed a Helm chart (the Element OnPrem server to be precise) which installs the following Ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: first-element-deployment-synapse
  namespace: element-onprem
spec:
  rules:
  - host: ***MASKED***
    http:
      paths:
      - backend:
          service:
            name: first-element-deployment-synapse-haproxy
            port:
              name: haproxy-http
        path: /_matrix
        pathType: Prefix
      - backend:
          service:
            name: first-element-deployment-synapse-haproxy
            port:
              name: haproxy-http
        path: /_synapse
        pathType: Prefix

Note that the service port is referenced by name and not by number. This breaks when using Caddy Ingress, which I figured would be due to the following line:

ingress/internal/caddy/ingress/reverseproxy.go

Line 34 in 908d854

clusterHostName := fmt.Sprintf("%v.%v.svc.cluster.local:%d", path.Backend.Service.Name, ing.Namespace, path.Backend.Service.Port.Number)

Basically it just returns port 0 here because the port number should be resolved by name instead of directly using the number.

@mavimo Would you be open to a PR to fix this?

[mavimo]

@lion7 I'll look into it soon, in the meantime if you have time to make a PR will be awesome! 🤩

[lion7]

I tried to fix it yesterday, but it proves to be a challenge since I don't have a k8s client available in reverseproxy.go. The ingress object itself is passed along via the Store thing without further, so I kind of got stuck.

I would need a k8s client to retrieve the Service itself from k8s and figure out the port number associated with the provided name. Perhaps you have some ideas that don't involve altering half of the codebase?