search

mattermost / mattermost-helm

Mattermost Helm charts for Kubernetes
Apache License 2.0
165 stars 147 forks source link

create new helm chart for deploying RTCD #331

Closed angeloskyratzakos closed 2 years ago

angeloskyratzakos commented 2 years ago

Summary

Create a new helm chart for deploying RTCD service

Ticket Link

https://mattermost.atlassian.net/browse/MM-43735

matrix-root commented 2 years ago

Hi! Am I right that I need deploy that RTCD if I want to use new beta-calls?

heyplusyou commented 2 years ago

Seems so, mattermost server does not have rtc udp port 8443, only this has. Could someone confirm setup?

onpaws commented 1 year ago

Is this chart intended for self-hosting users? If anyone has got it working would would appreciate your thoughts.

Been trying to follow these steps but no luck yet.

The good news is helm upgrade mattermost-rtcd mattermost/mattermost-rtcd -f mattermost-rtcd-values.yaml --namespace mattermost-rtcd --create-namespace --install --debug seemed to finish (🎉 ). The not so good news is calls are still ending after 10s, like they did before. I suspect UDP still isn't exposed because Mattermost client console log says:

com.mattermost.calls: rtc closed
com.mattermost.calls_20b1f0b7d4b3b754_bundle.js:2 com.mattermost.calls: disconnect

Where does this Ingress Class come from? image Should it not be just nginx? (cluster has Nginx Ingress installed).

Meanwhile the service AFAICT looks good.

image

So yeah, external traffic is apparently not hitting UDP port. Not sure where to look next 🤔 If anyone has any suggestions would be appreciated 🙏

Chart version: 1.1.1 mattermost-rtcd version: 0.7.0 Kubernetes: 1.24.4 Ingress: Nginx Ingress

mattermost-rtcd-values.yaml

image:
  repository: mattermost/rtcd
  tag: "v0.7.0"

ingress:
  enabled: true
  hosts:
    - host: mattermost-rtcd.mydomain.dev
      paths:
        - "/"