Releases: jitsi-contrib/jitsi-helm
v1.3.8
⚠️ BREAKING CHANGES ⚠️
This release changes the service template for Prosody StatefulSet, which is considered "illegal" by Kubernetes API and will block the upgrade unless you remove the StatefulSet first. To drop the StatefulSet while keeping all the pods/PVs/secrets intact, run this command:
kubectl -n ${jitsi_namespace} delete --cascade=orphan statefulset jitsi-meet-prosody
The --cascade=orphan
option will force K8s to only delete the StatefulSet itself, while keeping everything else intact. The Prosody pod will be recreated properly after you run the helm upgrade
command.
What's Changed
- Bump Jitsi Meet images to
stable-9111
; - Rework Prometheus template for JVB (thanks to @genofire in #94);
- Update Jitsi Meet exporter (thanks to @genofire in #91);
- Fix Prosody service name template (thanks to @wrenix in #87);
- Introduce a workaround for broken nginx regex preventing Colibri websockets from being proxied properly.
New Contributors
Full Changelog: v1.3.7...v1.3.8
Release v1.3.7
What's Changed
- Fix Prosody annotations to prevent it from restarting when it's not needed (thanks to @wrenix in #84);
New Contributors
Full Changelog: v1.3.6...v1.3.7
Release v1.3.6
What's Changed
- Update Jitsi Meet images to
stable-8719
; - Fix JVB pods being stuck in
Pending
state on upgrade when usinghostPort
s.
Full Changelog: v1.3.5...v1.3.6
Release v1.3.5
What's Changed
- Allow setting Jibri deployment's update strategy (thanks to @jmozd in #75);
- Fix outdated sections of the README;
- Add experimental signed provenance file to the chart.
New Contributors
Full Changelog: v1.3.4...v1.3.5
Release v1.3.4
What's Changed
- Bump Jitsi Meet images to
stable-8319
; - Add detailed Jibri instructions to README.md (thanks to @palmtown in #74);
Full Changelog: v1.3.3...v1.3.4
Release v1.3.3
What's Changed
- Bump Jitsi Meet images to
stable-8252
(thanks to @kpeiruza in #71); - Add a way to set
externalTrafficPolicy
for the JVB service (thanks to @mustdiechik in #68); - Add new knobs for Jibri recording and live streaming services;
- Add support for external Jibri deployments (thanks to @kpeiruza in #69).
New Contributors
- @mustdiechik made their first contribution in #68;
- @kpeiruza made their first contributions in #69 and #71.
Full Changelog: v1.3.2...v1.3.3
Release v1.3.2
⚠️ BREAKING CHANGES ⚠️
This release drops support for customizable Jicofo's XMPP user name (dropped in stable-8218
release of Jitsi Meet) and changes default thresholds for Jibri's liveness probes.
Jicofo XMPP user name is now hardcoded
Many internal parts of Jitsi Meet assume that Jicofo is always available via focus@<...>
JID, so upstream decided to hardcode it to avoid possible problems. The chart follows upstream's decision, so now JICOFO_AUTH_USER
is hardcoded to focus
as well.
Jibri liveness probes are now set to fail faster
Jibri used to have default settings for liveness/readiness probes (that is, delay=0s period=10s failure=3
), which is fine in most cases, but might be too slow when using the newly-introduced single-use mode. To account for this new feature, these probes are now set to execute every 5 seconds and fail after 2 unsuccessful tries, reducing possible Jibri downtime to ~10 seconds.
If you want to restore the previous behaviour, add this to your values.yaml
:
jibri:
livenessProbe:
# Recommended to leave this at default (5s),
# but...
initialDelaySeconds: 0
periodSeconds: 10
failureThreshold: 3
readinessProbe:
initialDelaySeconds: 0
periodSeconds: 10
failureThreshold: 3
What's changed
- Bump Jitsi Meet images to
stable-8218
; - Add support for Jibri's single-use mode;
- Drop support for deprecated Jicofo XMPP user setting;
Full Changelog: v1.3.1...v1.3.2
Release v1.3.1
⚠️ BREAKING CHANGES ⚠️
This release introduces support for multiple public IPs to be annotated by JVB. Because of this, the public IP syntax is changed.
Before:
jvb:
publicIP: 1.2.3.4
After:
jvb:
publicIPs:
- 1.2.3.4 # <- This IP will be used by legacy Jitsi Meet images
- 5.6.7.8
The support for configurable JVB server IDs has been removed. Now all JVB instances use their Pod IP as the server ID. Please remove the .Values.websockets.colibri.serverID
from your chart values/overrides.
What's Changed
- Fix Jitsi pods breakage after chart upgrade when using auto-generated passwords by annotating Prosody pod (fixes #16);
- Add support for new Ingress API introduced in Kubernetes v1.19.0;
- Always use internal pod IP address as JVB's server ID (useful for Colibri WebSocket transport);
- Add support for multiple public IPs.
Full Changelog: v1.3.0...v1.3.1
Release v1.3.0
⚠️ BREAKING CHANGES ⚠️
This release removes the old-style options located in .Values.jvb.websockets
.
Now, if you want to add WebSockets support, instead of doing this:
jvb:
websockets:
enabled: true
serverID: <...>
you must do this:
websockets:
colibri:
enabled: true
serverID: <...>
## New option for Prosody/XMPP:
xmpp:
enabled: true
Also, now disabled WS support explicitly sets required ENV variables to 'false', resulting in all Jitsi Meet containers actually using HTTP polling instead of WebSocket-based signalling.
What's Changed
- Fix helm test for prosody connection test by @hhewei in #51;
- Introduce separate node port value for JVB for Node by @luclu and @mmarquez999 in #25 and #54;
- Bump default Jitsi Meet version to
stable-8044
:jitsi/web:stable-8044
and newer can properly auto-detect the nameserver IP by reading/etc/resolv.conf
…- …so now there's no need to explicitly set
.Values.web.resolverIP
unless you really need to override it.
- Bump Jitsi Meet Prometheus Exporter to
v1.2.1
;
New Contributors
- @hhewei made their first contribution in #51;
- @luclu made their first contribution in #25;
- @mmarquez999 made their first contribution in #54;
Full Changelog: v1.2.3...v1.3.0
Release v1.2.3
What's Changed
Full Changelog: v1.2.2...v1.2.3