ESS Community Helm Chart 25.10.1 (2025-10-15)
Added
-
List deprecations in
NOTES.txtwhen runninghelm install/helm upgrade. (#796) -
Support overriding the default
imagePullPolicyfor every component by settingimage.pullPolicy.Per-image overrides can be set by setting
<path.to>.image.pullPolicyas before.If
image.pullPolicyor per-image overrides aren't setIfNotPresentis used by default for images
referenced by digest andAlwaysis used by default images referenced by tag as previously. (#798)
Changed
-
Update Matrix Authentication Service to v1.4.0.
Highlights:
- Make it possible to allow password registration without email verification.
- Add Admin API to finish individual sessions.
Full Changelogs:
(#787)
-
Ensure consistent captured headers in HAProxy log lines, between all HTTP request processing HAProxy frontends. (#788)
-
Correct the handling of multiple
X-Forwarded-Forheaders to Synapse.This may have exhibit itself as requests being incorrectly rate-limited by Synapse.
The source IP logged by HAProxy is now always the IP connecting to HAProxy rather than
a value extracted from theX-Forwarded-Forheader (if present). This is usually an IP
for the ingress controller. (#788) -
Log the
X-Forwarded-Forheader and stop logging theRefererheader in HAProxy. (#788) -
Upgrade HAProxy to 3.2.
Release notes:
(#790)
-
Upgrade Element Admin to v0.1.4.
Highlights:
- Use authenticated media endpoints for thumbnails
- Keep selected item when changing filters
Full Changelogs:
(#793)
-
Inform chart users, in
helm install/helm upgradenotes of the deprecations aroundrtc.{use_external_ip,node_ip}that happened in 25.9.1. (#796) -
Move the top-level
imagePullSecretslist toimage.pullSecrets.Setting
imagePullSecretsis deprecated and will be removed in 25.11. If you setimagePullSecretsin your values files, please migrate toimage.pullSecretsor you will see schema errors on upgrading to 25.11 when it is released. (#798) -
Upgrade Synapse to v1.140.0.
Highlights:
- Add a new Media Query by ID Admin API that allows server admins to query and investigate the metadata of local or cached remote media via the origin/media_id identifier found in a Matrix Content URI
- Add experimental implementation of the
GET /_matrix/client/v1/rtc/transportsendpoint for the latest draft of MSC4143: MatrixRTC
Full Changelogs:
(#799)
Fixed
- Fix templated
<component>.ingress.hostvalues not being rendered correctly inNOTES.txt. (#791) - Fix the Matrix RTC SFU not restarting when user-provided configuration is set via
matrixRTC.sfu.additional.<name>.config. (#805)
Internal
- CI: simplify the MatrixRTC integration test with Synapse + Well-Knowns. (#785)
- Ensure all
kubectlcommands inscripts/setup_test_cluster.shspecify the context. (#789) - CI: add a test that we don't have anything that looks like a template string in the rendered files. (#791)
- CI: check that all go files are formatted correctly as per
gofmt. (#792) - Run
gofmtovermatrix-tools. (#792) - CI: Use
poetry2.x. (#794) - CI: handle a user already existing in MAS across subsequent test runs. (#795)
- CI: recreate cached user access tokens when they're not valid (from a previous test run). (#795)
- CI: don't attempt to manage MAS user passwords if password login is disabled. (#795)
- CI: check that user-provided inline configuration changes a hash label on some workloads and thus restarts
Pods. (#805)