v0.6.0

This release brings the project up-to-date on several aspects:

Operator

• Updated Synapse to 1.222.0
• Updated Heisenbridge to 1.15
• Updated Mautrix-signal to 0.7.5, removing the need for deploying Signald

Development

• Updated to go 1.23 and dependencies, in particular controller-runtime to v0.20.0
• Updated controller-gen to 1.16.1, kusomize to v5.4.3, envtest to 1.31.0, operator-sdk to v1.29.0

v0.5.1

v0.5.0 & v0.5.1

This release contains a few user-facing changes:

• Secrets in homeserver.yaml are now randomly generated.
• When a bridge is deleted, it is now unregistered from Synapse.
• Update docker images to their latest available version to date, now deploying:
  • Synapse v1.82.0
  • Mautrix-signal v0.4.2
  • Signald 0.32.2
  • Heisenbridge 1.14 (no update since v0.4.0)

The focus has rahter been on various internal improvements and experiments:

• Improve overall sturcture and readability of the code base.
• Reduce code duplication.
• Use Embed.FS for templating Kubernetes resources rather than go structs.

And finally some development workflow improvements:

• Build and push the operator and bundle container images on release tags automatically using Github Action.
• Run unit and integration tests on commits and PR using GitHub Action.

v0.4.0

This release implements the necessary changes for the Synapse Operator to run on vanilla Kubernetes:

• Fix the permissions of the Service Account running the controllers.
• Only create Service Accounts for the Synapse and MautrixSignal pods if we're deploying on Openshift.
• Further minor code improvements

v0.3.0

• Move to a multi APIs architecture: Create new Heisenbridge and MautrixSignal resources to manage bridges.
• Adapt integration tests.
• Adapt examples.

v0.2.0

Notable changes:

• Add the option to deploy the mautrix-signal bridge.
• Extend and improve examples
• Move to a sub reconciler pattern to improve readability of the control loop
• Ensure user-provided ConfigMaps are not modified

v0.1.0

Very first release of the Synapse operator !

The main features included in this release are:

• Users can chose between:
  • Let the Synapse operator generate a homeserver.yaml configuration file by providing the required values in the Synapse CRD.
  • Or provide an existing homeserver.yaml.
• Users are able to request the deployment of a PostgreSQL DB to host the synapse database (relies on the postgres-operator).
• Users are able to request the deployment of the Heisenbridge.

This release also initializes the unit and integration test suite for the Synapse Operator.