HaProxy a must for Collabora/Code on Kubernetes?

Can I use Kong as Ingress Controller? Is this possible?

I dont have nor want HAProxy, I have my own Cloud based Loadbalancer.

If so I would fork and rewrite the helm chart and post them here, but I would need to know if this breaks anything.

Ok, small update. I managed to utilise Kong, and all pods are running, however when I use the URL in Nextcloud, nothing is happening, although I get the green check mark. Here is my Cluster Output:

NAME                                       READY   STATUS    RESTARTS   AGE
pod/collabora-myspace-74447bcbb-qbzgl   1/1     Running   0          17h
pod/collabora-myspace-74447bcbb-zbntd   1/1     Running   0          17h
pod/collabora-myspace-74447bcbb-zbtkc   1/1     Running   0          17h

NAME                           TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
service/collabora-myspace   ClusterIP   <none>        9980/TCP   17h

NAME                   CLASS   HOSTS                     ADDRESS                               PORTS     AGE
collabora-myspace   kong    collabora.myspace.de,2a01:4f8:1c1d:d41::1   80, 443   19h

Port 9980 enough? What am I missing here?

And what are these settings for

            - name: extra_params
              value: --o:ssl.enable=true
            - name: username
              value: jockel
            - name: password
              value: abcde
            - name: domain
              value: collabora.myspace.de

Do I need to use ssl.enable=true when I have a reverse proxy working?