github jitsi-contrib/jitsi-helm v3.3.0

latest releases: v3.14.0, v3.13.0, v3.12.0...
3 months ago

What's Changed

  • feat: upgrade Jitsi images to stable-11146-2
  • feat: update coturn to 4.17.2
  • feat: update etherpad to 3.3.3 (security release)
  • fix(templates): keep generated passwords across upgrades
  • fix(security): no container runs as root and no pod mounts a service account token
  • feat(templates): custom config file overrides for jvb, jigasi and transcriber
  • feat(prosody): support persistence.existingClaim

Any password left unset used to be regenerated on every render, which rewrote the secrets and rolled prosody, jvb, jicofo, jibri, jigasi, transcriber and coturn on each upgrade. They are now read back from the cluster and kept. The first upgrade to this version still rolls those pods once, which is expected.

⚠️ BREAKING CHANGES ⚠️

  • Requires stable-11146-2 images. Refresh any tag pins.
  • jibri.extraSecretsFrom is renamed to jibri.extraEnvFrom.
  • skynet.persistence.storageClass and transcriber.persistence.storageClass are renamed to storageClassName.
  • prosody.extraVolumeClaimTemplates was removed. Use prosody.extraVolumes and prosody.extraVolumeMounts.
  • jibri.persistence.accessModes is configurable and defaults to [ReadWriteMany]. A PVC's access modes cannot be patched, so pin [ReadWriteOnce, ReadWriteMany] to keep an existing claim.
  • extraEnvFrom is now honoured by web, jvb, jicofo, coturn, etherpad and excalidraw, which ignored it before. Values you set there now take effect.
  • No pod mounts a ServiceAccount token.
  • Prosody keeps its data in the data subfolder of /var/lib/prosody. Service accounts re-register themselves; move hand-registered internal_hashed accounts into data/ once.

Full Changelog: v3.2.0...v3.3.0

Don't miss a new jitsi-helm release

NewReleases is sending notifications on new releases.