Fork helm chart for matrix synapse #3

Add https://github.com/tulir/mautrix-whatsapp and start laying some groundwork for future bridges. Bridge is disabled by default.

Added port 3748 to Coturn and configured as a NodePort. This is the default port for STUN connections, ports 49152-49172 are only used after a connection has been established and authenticated.

Fixed Synapse being stuck in pending when bridges were disabled, due to it waiting for the bridge registration file PVC.

LoadBalancers usually spin up additional infrastructure, which can be expensive. Change the default type to a NodePort for fewer heart attacks.

Set LC_COLLATION and LC_CTYPE to 'C' for the matrix database when using stable/postgresql. Synapse 1.10 and above requires this.

The "matrix.baseUrl" template is used to determine the URL of the synapse instance in a few places. It needs to start with https://, but the ingress definition only contains a hostname.

Closes #11

DigitalOcean K8s doesn't support the ReadWriteMany access mode for PVCs. This is required to share bridge/appservice registration files with Synapse, as the bridge pods are not necessarily scheduled on the same node as Synapse. The workaround was to: - Add an override to change the access mode of the bridge PVC in values.yaml - Add a setting to configure affinity between bridges and Synapse, so that this access mode is actually valid DOK8S also requires a minimum PVC size of 1Gi. Added an override for the size of the bridge PVC, but left the default at 1Mi.

@danjenkins

Add support for running Coturn pods under a DaemonSet with host networking enabled to bind TURN ports on each node. This maximizes compatibility as it doesn't require setting the NodePort range setting on the cluster as a whole. The downside is that it will deploy one Coturn pod for each node, which may be more (or fewer) than necessary, so the old method of Deployment + NodePort is still supported. Thanks to @danjenkins for this one.

@danjenkins

Added the official Matrix.org IRC appservice. Thanks to @danjenkins for the majority of this commit!

This runs federation behind the Ingress, at port 443 but on a different subdomain. This will allow users to deploy a federating homeserver *without* needing to pay for/configure TLS for an external load balancer.

When using nginx-ingress-provider, nginx may overwrite non-200 responses and replace the expected JSON schema. This breaks spec, and has broken some of the _matrix/key endpoints.

This is needed for anyone running Coturn at a different hostname, as well as anyone running an external Coturn instance.

…the orginal deployment in order to release the ReadWriteOnce PVC on the bridges.

…SSL verification if needed

…heus-operator ServiceMonitors

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fork helm chart for matrix synapse #3

Fork helm chart for matrix synapse #3

Commits on Jun 26, 2022

Fork helm chart for matrix synapse #3

Are you sure you want to change the base?

Fork helm chart for matrix synapse #3

Commits on Jun 26, 2022