search

blakeblackshear / blakeshome-charts

Repo for helm charts
41 stars 52 forks source link

support webrtc #49

Open mvivaldi opened 10 months ago

mvivaldi commented 10 months ago

I'm not well-versed in Helm, and I haven't had a chance to validate the suggested modifications. However, I applied a patch to my Kubernetes service directly, configuring it to support WebRTC with a LoadBalancer service type.

I'm uncertain whether it's advisable to enable the WebRTC section exclusively when using a LoadBalancer service type. Initially, my intention was simply to raise an issue requesting WebRTC support. Surprisingly, I experimented with this approach, and it successfully functioned on my microk8s instance.

ekozan commented 10 months ago

you need to modify the deployment too ;)

evanjarrett commented 7 months ago

You can share the same ports on Deployments and Services, you just cannot patch them. The only way is to delete and recreate the resource

k get svc
NAME      TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)                                                                      AGE
frigate   LoadBalancer   10.43.74.206   10.11.12.13   5000:30446/TCP,1935:30331/TCP,8554:30421/TCP,8555:30505/UDP,8555:30505/TCP   4s

That said, I've spent a good chunk of time working on this, and while exposing port 8555 is progress, I can't seem to get webrtc to work fully through kubernetes. I believe it might be possible with host networking, but I'm not going to enable that on my cluster.

hagak commented 4 months ago

Could you used MetalLB and loadbalancer to allow networking without host networking?