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-2images. Refresh any tag pins. jibri.extraSecretsFromis renamed tojibri.extraEnvFrom.skynet.persistence.storageClassandtranscriber.persistence.storageClassare renamed tostorageClassName.prosody.extraVolumeClaimTemplateswas removed. Useprosody.extraVolumesandprosody.extraVolumeMounts.jibri.persistence.accessModesis configurable and defaults to[ReadWriteMany]. A PVC's access modes cannot be patched, so pin[ReadWriteOnce, ReadWriteMany]to keep an existing claim.extraEnvFromis 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
datasubfolder of/var/lib/prosody. Service accounts re-register themselves; move hand-registeredinternal_hashedaccounts intodata/once.
Full Changelog: v3.2.0...v3.3.0