This message was deleted.
# helpdesks
steep-balloon-41261
11/16/2022, 1:13 PMThis message was deleted.
a
acoustic-boots-6423
11/16/2022, 4:55 PMHey, I am running a similar setup successfully. It might not be the best setup for performance but it works. Here are the changes required, pending a review and hopefully a merge.
r
rich-pharmacist-13082
11/17/2022, 8:48 AMThanks for the reply. What I fail to understand is how to correctly exchange IP/Connection info for clients if nodes can't open ports as they like. Do you tunnel everything through nginx/LB?
a
acoustic-boots-6423
11/17/2022, 9:15 AM@rich-pharmacist-13082 correct: https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/
r
rich-pharmacist-13082
11/17/2022, 9:44 AMWould you happen to have the Service/Ingress config you use available? I'm aware of this nginx functionality but wonder how to correctly implement it with livekit
a
acoustic-boots-6423
11/17/2022, 2:14 PMwith the PR, this should be enough for the service, you only need to add the exposing to your ingress-nginx config
acoustic-boots-6423
11/17/2022, 2:14 PMthen something like
Copy code
apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
name: livekit-server
namespace: ${module.config.values.namespace}
annotations:
<http://cert-manager.io/cluster-issuer|cert-manager.io/cluster-issuer>: letsencrypt
<http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout>: 3600
<http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout>: 3600
spec:
ingressClassName: nginx
tls:
- hosts:
- ${module.config.values.domain_live}
secretName: live-tls
rules:
- host: ${module.config.values.domain_live}
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: livekit-livekit-server
port:
number: 80r
rich-pharmacist-13082
11/18/2022, 9:20 AMThanks for the info, I'll see if I can get it done
m
microscopic-dusk-5190
11/21/2022, 4:02 PMHi @rich-pharmacist-13082 we have been playing around with STUNner and Livekit to get rid of the "direct reachability" problem in k8s, and we used LB service and nodePort. However, we took some steps to test it with metalLB (paused right now), feel free to open an issue here if you feel like it could be useful feature for you:
https://github.com/l7mp/stunner/tree/main/examples/livekit