Jitsi Meet Helm Chart

The chart supports bridge-based near real-time transcription (subtitles).

How it works:

1. Jicofo instructs JVB which transcription service to use for a conference.
2. JVB streams audio to opus-transcriber-proxy.
3. The proxy relays audio to a speech-to-text provider (OpenAI, Deepgram, Gemini) or a custom OpenAI-compatible service.

Setup requirements:

• Set opusTranscriberProxy.enabled to true.
• Manual Step: You must manually enable the force_async_transcription Prosody module; the chart does not enable this automatically.

The JVB (Jitsi Videobridge) scaling mechanism has been updated. You can now use jvb.portRangeSize to run multiple JVBs behind a single Service. Each JVB will receive its own unique port, and the Service will publish all of them.

Important Constraints:

• Naming: The JVB UDP container port is now named rtp-udp-0 (previously rtp-udp). Update any NetworkPolicies that use named ports.
• Replica Conflict: If you set jvb.replicaCount greater than 1 while the JVB Service is enabled, the Helm render will fail. To run multiple JVBs, you must use portRangeSize instead of increasing replicaCount (unless using useHostPort).
• NodePort: If using a NodePort Service, ensure nodePort is set equal to UDPPort so advertised and reachable ports match.

Non-root containers cannot bind to ports below 1024. To accommodate this, the chart listens on unprivileged ports inside the container and uses a Kubernetes Service to map public ports to them (e.g., web listens on 8000, and coTURN listens on 3478 behind a Service on 443).

If you use hostNetwork: true or hostPort, the Service translation is bypassed. In such cases, if you need to bind to a public port below 1024, you must set runAsUser: 0 for that component.

Jigasi-based transcription (used by Transcriber and Skynet) is deprecated and will be removed in a future release.

Recommendation: New deployments should use the bridge-based path via opusTranscriberProxy. Existing setups will continue to work for now, but you should plan a migration to the new path.

Scaling strategies differ based on the component:

• Stateless Components: Jitsi Web, Jibri, and Coturn can be scaled freely by adjusting their replicaCount.
• JVB (Videobridge): Scales via the OCTO relay feature, which distributes participants of a single meeting across multiple bridges. JVB can also scale based on load and supports 'draining' to ensure existing calls are not dropped when a bridge is removed.

The Chart.yaml file contains two distinct versioning fields that affect how images are pulled:

1. version: The version of the Helm chart itself. This is incremented whenever the chart code changes.
2. appVersion: The default image tag used for core Jitsi components (web, prosody, jvb, jicofo, jigasi, jibri) if you have not explicitly set an image.tag in your values.yaml.

Note: Third-party components (like coturn, etherpad, excalidraw, or Skynet) are pinned to their own specific image.tag in values.yaml and are independent of the appVersion field.

The Jitsi Videobridge (JVB) must be reachable by all participants, typically via a public IP. The Helm chart supports several methods for exposing JVB:

• LoadBalancer
• NodePort
• hostPort (supports auto-detected node IP and port ranges)
• hostNetwork
• Ingress TCP/UDP forwarding

Refer to the detailed Exposing guide for specific configuration examples for each method.

Use this option to expose JVB via a specific port on your cluster nodes or through an external LoadBalancer pointing to the nodes.

Configuration Rules:

• jvb.replicaCount must remain at 1 unless using jvb.portRangeSize.
• If using jvb.portRangeSize > 1, you must set both jvb.UDPPort and jvb.nodePort to the same base value. This ensures the advertised port and the node port match for the consecutive range.
• Every port in the range must be within the cluster's allowed NodePort range (default 30000-32767).

# Single JVB instance
jvb:
  service:
    type: NodePort
  publicIPs:
    - 30.10.10.1

# Multiple JVB instances using a port range
jvb:
  UDPPort: 32000
  nodePort: 32000
  portRangeSize: 3
  service:
    type: NodePort
  publicIPs:
    - 30.10.10.1

If you prefer to keep the JVB service enabled (e.g., using type: LoadBalancer), you cannot use replicaCount because all pods in a deployment would share the same service port. Instead, use portRangeSize. This configuration deploys one JVB per port within a specified range, and the service publishes all of them.

Example for 3 JVBs listening on 10000/UDP, 10001/UDP, and 10002/UDP:

jvb:
  # 3 JVBs, listening on 10000/UDP, 10001/UDP and 10002/UDP
  UDPPort: 10000
  portRangeSize: 3

  service:
    type: LoadBalancer

octo:
  enabled: true

To extend your Jitsi Meet installation with additional Prosody features, you can mount custom Lua modules using extraVolumes and extraVolumeMounts in your Helm chart configuration. This allows you to inject specific .lua files from a ConfigMap into the Prosody container's file system.

Note: If you are looking for plugins from the jitsi-contrib/prosody-plugins repository, they are already included in the official ghcr.io/jitsi/prosody container and do not need to be added manually.

prosody:
  extraVolumes:
    - name: prosody-modules
      configMap:
        name: prosody-modules

  extraVolumeMounts:
    - name: prosody-modules
      subPath: mod_measure_client_presence.lua
      mountPath: /prosody-plugins-custom/mod_measure_client_presence.lua