Deploy the official Matrix Stack helm chart #1
eric
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There appears to be an official chart for the entire Matrix stack. Given some of the complications with the existing chart, it may be worth migrating to this one. Retaining data will be challenging but informative.
This is a duplicate of DevOps/ansible-role-eom#32.
Helm Chartto Deploy the official Matrix Stack helm chartMatrix Stack Helm Chart Configuration
Chapters
0:00:00 Intro
0:08:25 Matrix stack overview
0:18:53 Global configuration
0:36:45 MatrixRTC
0:45:51 Element Web
0:48:12 HAProxy
0:52:40 Matrix Authentication Service
0:58:50 PostgreSQL
1:03:50 Synapse
1:09:30 Well-known delegation
1:17:00 Outro
Summary
This live stream was hosted on Owncast and covers the initial configuration for the Matrix Stack Helm chart. An overview of the Matrix stack is provided, but for the most part, I am just going through the default
values.yamlprovided by the chart, populating important fields, and removing unnecessary ones. Having deployed Matrix previously through a different chart, I am thinking through options for migrating existing accounts, rooms, and spaces to the new deployment, though it may be necessary to start over with a fresh installation, which may also cause issues with existing federated chats. I am going to take some time to consider the best path forward before continuing.Deploying Matrix Stack to Kubernetes
Chapters
00:00:00 Matrix Authentication Service Configuration
00:32:49 Deploying Matrix to Kubernetes
01:39:52 Reconfigure MAS
02:17:57 Debugging existing chats
Summary
In this live stream I am replacing my existing Matrix deployment with the configuration I began in the previous video. I add a few values for SMTP services and an upstream OAuth2 provider to enable SSO with Google. While SSO was successful, I had difficulty connecting with a user with whom I previously chatted due to my identity being reset. Upon further testing, I discovered I was also unable to join public Matrix spaces hosted on matrix.org. I suspect the federation key from the previous deployment needs to be recovered in order to reestablish these connections. Hopefully the previous key can be recovered from the Kubernetes PVC archive so that I can reconnect with other Matrix users.
Deployment is working and federated chats are behaving as expected as well (I suspect caching had something to do with the issue here). I am closing this issue and will open additional ones to address specific concerns on this platform.