This message was deleted.
# announcements
s
This message was deleted.
s
It seems Linode is also having this limitation, as per this conversation with @adorable-printer-44453 : https://livekit-users.slack.com/archives/C01KZ61HZRR/p1644542663306799?thread_ts=1642638629.038200&cid=C01KZ61HZRR
a
Yup, seems either GCP or AWS, GCP worked well with me
s
How about pricing?
It seems Vultr has the same limitation:
What protocols do you support?
Vultr Load Balancers support TCP, HTTP, and HTTPS.
https://www.vultr.com/docs/vultr-load-balancers
Confirming Vultr, customer support told me they don't have that feature available.
d
Erick, you do not want to put a load balancer in front of LiveKit UDP ports. instead they need to be exposed and accessible from the internet. See Ports docs
👍 1
a
@some-greece-49743 Please don’t deploy to k8s, my advise is to talk to our friend @dry-elephant-14928 and ask about alternative cloud options 🙂
d
As @dry-elephant-14928 mentioned, you don't need any load balancer for UDP. For my case I'm using haproxy which is handling 443 port & forward to livekit cluster. Everything else is handling by livekit itself because livekit instances have their own IP address & in firewall I opened only UDP port. For my case I'm also using haproxy for Turn server forward too but I also tried with external turn server.
s
Thanks @dry-elephant-14928.
@adorable-printer-44453, GKE is interesting but could be expensive.
Thanks @damp-postman-69501. Are you using a single node?
d
I tested with different scenario. Honestly I never used K8s. For livekit I'm using multiple servers which is connected with single redis. I used single server to configure haproxy + redis.
s
Ok.
Interesting.
So @damp-postman-69501, you basically configure multiple services (Livekit VM config?) and use redis using that setup, right?
d
yes, like that.
s
Thanks. I'll try that and see what happens.