jitsi-contrib/jitsi-helm v3.1.0

on GitHub

What's Changed

• feat(jvb): multiple JVBs on a single LoadBalancer service
• docs(values): Describe portRangeSize as the JVB scaling knob

jvb.portRangeSize is no longer tied to useHostPort. Each JVB gets its own UDP port and the same service publishes all of them. So, one LoadBalancer IP now serves every bridge. See Scaling guide.

⚠️ BREAKING CHANGES ⚠️

• JVB's UDP container port is now named rtp-udp-0 (was rtp-udp), with one named port per JVB. Update anything referring to the old name, such as a NetworkPolicy using named ports
• jvb.portRangeSize greater than 1 without useHostPort used to be silently ignored and is now honoured, so you get that many JVBs, pods and Service ports
• jvb.replicaCount greater than 1 with the JVB Service enabled now fails the render instead of deploying. Use portRangeSize, or keep replicaCount with useHostPort
• With a NodePort Service, jvb.nodePort is the base of a consecutive range; keep it equal to UDPPort so the advertised and reachable ports match

Full Changelog: v3.0.2...v3.1.0