feat: basic support for federation

[debdutdeb]

This is a very basic support to quickly enable federation in your deployment.

To configure the deployment, add the following to the values file -

host: ... # this is a must for federation as https is required
ingress:
  enabled: true
  annotations:
    cert-manager.io/cluster-issuer: some-issuer # or some other annotation if using annotation based automatic certificate assignment
  tls:
    hosts:
      - ... # the value of host
      - ... # value of the domain where matrix will be accessible from

federation:
  enabled: true
  host: ... # some host where your synapse install will be accessible from
  persistence:
    enabled: true
    existingClaim: ... # some claim

[geekgonecrazy]

I'm very hesitant to give thumbs up on this. SQLite is awesome.. but its not the recommended way by MatrixOrg / Element. So I don't think we should be letting people set it up in a non-recommended way.

If you want to add a flag for "useSQLite: true" for people that wish to only use SQLite then go for it. But the default should be postgres

[geekgonecrazy]

Per above suggestions

[debdutdeb]

host: rocketchat-fed.dev.rocket.chat

externalMongodbUrl: <RADACTED>
externalMongodbOplogUrl: <REDACTED>

ingress:
  enabled: true
  ingressClassName: nginx
  annotations:
    cert-manager.io/cluster-issuer: production-cert-issuer
  tls:
    - secretName: some-secret
      hosts:
        - rocketchat-fed.dev.rocket.chat
        - matrix-fed.dev.rocket.chat


microservices:
  enabled: false


mongodb:
  enabled: false

federation:
  enabled: true
  host: matrix-fed.dev.rocket.chat
  persistence:
    enabled: true
    existingClaim: synapse-helm

[debdutdeb]

self note: add the documentation for the settings

[debdutdeb]

This isn't implemented yet, we will be able to avoid litghttpd and other ingress configs this way.

pr isn't merged yet RocketChat/Rocket.Chat#31965

Idea was to make this default for chart installs, but we need this now and can make it opt in.

[geekgonecrazy]

I'd like to see that lighthttpd instance go away. But I guess we have to wait until 6.7 for that.

I wish element or matrix.org had an official chart for this. But can't find anything other than this ai hallucination https://www.pulumi.com/ai/answers/bUXpwtGTrLbRSFk1Lzkwt2/managing-helm-chart-deployments-on-kubernetes

Overall I don't like this extra complexity being brought in to our chart.. But its necessary for a better customer experience. K8S can be tricky, and deploying federation even more tricky.

I guess lets do this ✅