Skip to content

Draft: Rework Calls Deployment Guide #8879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
esethna wants to merge 46 commits into
base: master
Choose a base branch
from
Open

Draft: Rework Calls Deployment Guide #8879

Show file tree
Hide file tree
Changes from 23 commits
Commits
Show all changes
46 commits
Select commit Hold shift + click to select a range
9fa3794
calls-deploy-rewritev6
esethna Apr 12, 2026
9a2ed57
mermaid tweaks
esethna Apr 12, 2026
0d96b59
mermaid-test
esethna Apr 12, 2026
4835b64
1.6 checks
esethna Apr 12, 2026
89a8386
tweaks
esethna Apr 12, 2026
4da4a85
tweaks
esethna Apr 12, 2026
a298cbd
tweaks
esethna Apr 12, 2026
be54c5a
tweaks
esethna Apr 12, 2026
855e76e
tweaks
esethna Apr 12, 2026
3ebb08a
review tweaks
esethna Apr 12, 2026
62030ec
diagrams-test
esethna Apr 12, 2026
beabac2
replace mermaid diagrams
esethna Apr 13, 2026
fb0154b
checkboxes and images
esethna Apr 13, 2026
67c50de
logging redirect
esethna Apr 13, 2026
aacd90f
tweaks
esethna Apr 13, 2026
ce98172
tweaks tables
esethna Apr 13, 2026
8a5caef
editor tweaks
esethna Apr 13, 2026
360f42a
tweaks
esethna Apr 13, 2026
ea585a9
tweaks
esethna Apr 13, 2026
8f72dd8
editor tweaks
esethna Apr 13, 2026
12d2864
LHS nav + link redirects
esethna Apr 14, 2026
fe36000
Merge branch 'master' into calls-deploy-v6
esethna Apr 14, 2026
2f420ba
Merge branch 'master' into calls-deploy-v6
esethna Apr 14, 2026
c6d90dc
Merge branch 'master' into calls-deploy-v6
esethna Apr 15, 2026
0b53f3f
add calls SME persona
esethna Apr 15, 2026
123e2ec
commit feedback
esethna Apr 17, 2026
42fae25
Merge branch 'master' into calls-deploy-v6
esethna Apr 17, 2026
3e209ae
tweaks
esethna Apr 17, 2026
f3e9de7
tweaks
esethna Apr 17, 2026
820d2b2
tweaks
esethna Apr 17, 2026
83791ad
tweaks
esethna Apr 17, 2026
7b5e793
tweaks
esethna Apr 17, 2026
e669e17
fix tabs
esethna Apr 17, 2026
06952dd
fix images
esethna Apr 17, 2026
57116d4
Merge remote-tracking branch 'origin/master' into calls-deploy-v6
esethna Apr 17, 2026
9476157
Merge branch 'master' into calls-deploy-v6
esethna Apr 17, 2026
ca625e7
Merge branch 'master' into calls-deploy-v6
esethna Apr 21, 2026
3990143
update diagrams
esethna Apr 21, 2026
cb7888a
image size adjust
esethna Apr 21, 2026
84a1c5c
security-sam review
esethna Apr 21, 2026
44c378f
Merge branch 'master' into calls-deploy-v6
esethna Apr 23, 2026
4aa7aaf
Path overview tweaks
esethna Apr 23, 2026
89ff2ac
tab tweaks
esethna Apr 23, 2026
483cea6
tweaks
esethna Apr 23, 2026
5d733f2
link fixes
esethna Apr 23, 2026
6fbaee9
tweaks
esethna Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions source/_static/css/homepage-v1.css
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

863 changes: 863 additions & 0 deletions source/administration-guide/configure/calls-deployment-guide.md
View file
Open in desktop

Large diffs are not rendered by default.

334 changes: 0 additions & 334 deletions source/administration-guide/configure/calls-deployment.md
View file
Open in desktop

This file was deleted.

6 changes: 3 additions & 3 deletions source/administration-guide/configure/calls-kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,12 +99,12 @@ For Kubernetes-specific troubleshooting:
3. Ensure UDP and TCP traffic is properly routed through your load balancer
4. Verify network policies allow required communication paths

For detailed troubleshooting steps, see the [Calls Troubleshooting](calls-troubleshooting.md) guide.
For detailed logging guidance, see the [Calls Logging](calls-logging.md) guide.

## Other Calls Documentation

- [Calls Overview](calls-deployment.md): Overview of deployment options and architecture
- [Calls Deployment Guide](calls-deployment-guide.md): Overview of deployment options and architecture
- [RTCD Setup and Configuration](calls-rtcd-setup.md): Comprehensive guide for setting up the dedicated RTCD service
- [Calls Offloader Setup and Configuration](calls-offloader-setup.md): Setup guide for call recording and transcription
- [Calls Metrics and Monitoring](calls-metrics-monitoring.md): Guide to monitoring Calls performance using metrics and observability
- [Calls Troubleshooting](calls-troubleshooting.md): Detailed troubleshooting steps and debugging techniques
- [Calls Logging](calls-logging.md): Detailed guidance for collecting Calls logs and client diagnostics
4 changes: 2 additions & 2 deletions ...-guide/configure/calls-troubleshooting.md → ...stration-guide/configure/calls-logging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Troubleshooting Mattermost Calls
# Calls Logging

```{include} ../../_static/badges/all-commercial.md
```
Expand Down Expand Up @@ -29,4 +29,4 @@ The Mattermost server logs often contain entries related to the Calls plugin. If

```{note}
Interpreting RTCD and client logs can be challenging, as the Interactive Connectivity Establishment (ICE) negotiation during call setup often logs expected and benign failure or error messages. We strongly recommend providing the complete set of logs to Mattermost Support for analysis.
```
```
Comment on lines 30 to +32
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Use a security-focused callout for full-log sharing guidance.

Line 31 currently tells users to provide the complete logs, but this can expose sensitive data (tokens, internal hostnames, user identifiers, IPs). This should be a warning (not a note) and include a short sanitization/secure-sharing instruction.

Suggested minimal diff 
-```{note}
-Interpreting RTCD and client logs can be challenging, as the Interactive Connectivity Establishment (ICE) negotiation during call setup often logs expected and benign failure or error messages. We strongly recommend providing the complete set of logs to Mattermost Support for analysis.
+```{warning}
+Interpreting RTCD and client logs can be challenging, as the Interactive Connectivity Establishment (ICE) negotiation during call setup often logs expected and benign failure or error messages. Share logs only through approved support channels, and sanitize secrets, tokens, internal hostnames, and user-identifying data before sharing.
</details>

 
As per coding guidelines, “Use warnings and important callouts in documentation when a mistake could create security exposure” and “Reference secrets with secure handling practices in documentation, not pasted casually into examples.”

<details>
<summary>🤖 Prompt for AI Agents</summary>

Verify each finding against the current code and only fix it if needed.

In @source/administration-guide/configure/calls-logging.md around lines 30 - 32,
The current documentation callout uses a benign note and instructs users to
"provide the complete set of logs", which can leak secrets; change the callout
token from {note} to {warning} and update the message in the RTCD/client logs
block to instruct users to only share logs via approved support channels and to
sanitize/remove secrets, tokens, internal hostnames, IPs and user-identifying
data before sharing — locate and edit the fenced block that begins with
{note} (the RTCD/client logs paragraph) to use {warning} and append the
short secure-sharing/sanitization guidance.


</details>

<!-- fingerprinting:phantom:triton:hawk:bbeb82f7-e101-49b3-b8b2-5c83db9cb660 -->

<!-- This is an auto-generated comment by CodeRabbit -->

4 changes: 2 additions & 2 deletions source/administration-guide/configure/calls-metrics-monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -408,11 +408,11 @@ Each target should show status "UP" in green. If a target shows "DOWN" or errors

## Other Calls Documentation

- [Calls Overview](calls-deployment.md): Overview of deployment options and architecture
- [Calls Deployment Guide](calls-deployment-guide.md): Overview of deployment options and architecture
- [RTCD Setup and Configuration](calls-rtcd-setup.md): Comprehensive guide for setting up the dedicated RTCD service
- [Calls Offloader Setup and Configuration](calls-offloader-setup.md): Setup guide for call recording and transcription
- [Calls Deployment on Kubernetes](calls-kubernetes.md): Detailed guide for deploying Calls in Kubernetes environments
- [Calls Troubleshooting](calls-troubleshooting.md): Detailed troubleshooting steps and debugging techniques
- [Calls Logging](calls-logging.md): Detailed guidance for collecting Calls logs and client diagnostics

**Note:**
Configure Prometheus storage accordingly to balance disk usage with retention needs. If you need to be tight on storage, you can use a short retention period. If you have lots of storage you can keep the retention length longer.
4 changes: 2 additions & 2 deletions source/administration-guide/configure/calls-offloader-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -493,9 +493,9 @@ The `--image-registry` flag sets the registry prefix used when the offloader pul

## Other Calls Documentation

- [Calls Overview](calls-deployment.md): Overview of deployment options and architecture
- [Calls Deployment Guide](calls-deployment-guide.md): Overview of deployment options and architecture
- [RTCD Setup and Configuration](calls-rtcd-setup.md): Comprehensive guide for setting up the dedicated RTCD service
- [Calls Metrics and Monitoring](calls-metrics-monitoring.md): Guide to monitoring Calls performance using metrics and observability
- [Calls Deployment on Kubernetes](calls-kubernetes.md): Detailed guide for deploying Calls in Kubernetes environments
- [Calls Troubleshooting](calls-troubleshooting.md): Detailed troubleshooting steps and debugging techniques
- [Calls Logging](calls-logging.md): Detailed guidance for collecting Calls logs and client diagnostics
- [calls-offloader performance documentation](https://github.com/mattermost/calls-offloader/blob/master/docs/performance.md): Detailed performance tuning and monitoring recommendations
27 changes: 0 additions & 27 deletions source/administration-guide/configure/calls-overview.rst
View file
Open in desktop

This file was deleted.

6 changes: 3 additions & 3 deletions source/administration-guide/configure/calls-rtcd-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This guide provides detailed instructions for setting up, configuring, and valid
Before deploying RTCD, ensure you have:

- A Mattermost Enterprise license
- A server or VM with sufficient CPU and network capacity (see the [Performance](calls-deployment.html#performance) section for sizing guidance)
- A server or VM with sufficient CPU and network capacity (see the [Performance baselines](calls-metrics-monitoring.md#performance-baselines) section for sizing guidance)

## Network Requirements

Expand Down Expand Up @@ -373,10 +373,10 @@ Once RTCD is properly set up and validated, configure Mattermost to use it:

## Other Calls Documentation

- [Calls Overview](calls-deployment.md): Overview of deployment options and architecture
- [Calls Deployment Guide](calls-deployment-guide.md): Overview of deployment options and architecture
- [Calls Offloader Setup and Configuration](calls-offloader-setup.md): Setup guide for call recording and transcription
- [Calls Metrics and Monitoring](calls-metrics-monitoring.md): Guide to monitoring Calls performance using metrics and observability
- [Calls Deployment on Kubernetes](calls-kubernetes.md): Detailed guide for deploying Calls in Kubernetes environments
- [Calls Troubleshooting](calls-troubleshooting.md): Detailed troubleshooting steps and debugging techniques
- [Calls Logging](calls-logging.md): Detailed guidance for collecting Calls logs and client diagnostics

For detailed Mattermost Calls configuration options, see the [Calls Plugin Configuration Settings](plugins-configuration-settings.rst#calls) documentation.
10 changes: 5 additions & 5 deletions source/administration-guide/configure/plugins-configuration-settings.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -482,7 +482,7 @@ Max call participants
.. note::
- This setting is applicable only to self-hosted deployments.
- The environment variable ``MM_CALLS_MAX_PARTICIPANTS`` is deprecated in favor of ``MM_CALLS_MAX_CALL_PARTICIPANTS``.
- This setting is optional, but the recommended maximum number of participants is **50**. Call participant limits greatly depends on instance resources. See the :doc:`Calls self-hosted deployment </administration-guide/configure/calls-deployment>` documentation for details.
- This setting is optional, but the recommended maximum number of participants is **50**. Call participant limits greatly depends on instance resources. See the :doc:`Calls deployment guide </administration-guide/configure/calls-deployment-guide>` documentation for details.
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix the grammar in the participant-limit note.

“Limits” is plural, so “depends” should be “depend”.

Suggested edit 
-  - This setting is optional, but the recommended maximum number of participants is **50**. Call participant limits greatly depends on instance resources. See the :doc:`Calls deployment guide </administration-guide/configure/calls-deployment-guide>` documentation for details.
+  - This setting is optional, but the recommended maximum number of participants is **50**. Call participant limits depend greatly on instance resources. See the :doc:`Calls deployment guide </administration-guide/configure/calls-deployment-guide>` documentation for details.

As per coding guidelines, “Flag awkward phrasing, punctuation mistakes, tense shifts, and terminology inconsistencies in documentation.”

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- This setting is optional, but the recommended maximum number of participants is **50**. Call participant limits greatly depends on instance resources. See the :doc:`Calls deployment guide </administration-guide/configure/calls-deployment-guide>` documentation for details.
- This setting is optional, but the recommended maximum number of participants is **50**. Call participant limits depend greatly on instance resources. See the :doc:`Calls deployment guide </administration-guide/configure/calls-deployment-guide>` documentation for details.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@source/administration-guide/configure/plugins-configuration-settings.rst` at
line 485, Fix the grammar in the participant-limit note by changing "Call
participant limits greatly depends on instance resources." to "Call participant
limits greatly depend on instance resources." so the plural subject "limits"
agrees with the verb "depend"; update the sentence in the same paragraph near
the participant limit recommendation (the line containing "This setting is
optional, but the recommended maximum number of participants is **50**. Call
participant limits greatly depends on instance resources.") to use "depend".



.. config:setting:: ice-servers-configurations
Expand Down Expand Up @@ -510,7 +510,7 @@ ICE servers configurations
- The configurations above, containing STUN and TURN servers, are sent to the clients and used to generate local candidates.
- If hosting calls through the plugin (i.e. not using the |rtcd_service|) any configured STUN server may also be used to find the instance's public IP when none is provided through the |ice_host_override_link| option.

.. |rtcd_service| replace:: :doc:`RTCD service </administration-guide/configure/calls-deployment>`
.. |rtcd_service| replace:: :doc:`RTCD service </administration-guide/configure/calls-deployment-guide>`
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Point the |rtcd_service| shortcut to the dedicated RTCD guide.

This replacement is used in configuration notes specifically about the standalone rtcd service, so routing readers to the general deployment guide makes the link less precise.

Suggested fix 
-.. |rtcd_service| replace:: :doc:`RTCD service </administration-guide/configure/calls-deployment-guide>`
+.. |rtcd_service| replace:: :doc:`RTCD service </administration-guide/configure/calls-rtcd-setup>`

As per coding guidelines, “When a docs link is broken, brittle, or non-standard, explain the issue briefly and provide the smallest correct replacement.”

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@source/administration-guide/configure/plugins-configuration-settings.rst` at
line 513, The |rtcd_service| replacement currently points to the general calls
deployment guide; update the replacement so the shortcut links to the dedicated
RTCD guide instead (replace ":doc:`RTCD service
</administration-guide/configure/calls-deployment-guide>`" with a doc reference
that targets the standalone RTCD guide page), editing the |rtcd_service|
replacement line in the file so all notes about the standalone rtcd service
point to the precise RTCD guide.


**Example**

Expand Down Expand Up @@ -758,7 +758,7 @@ Call recording quality

.. note::
- This setting is applicable only to self-hosted deployments.
- The quality setting will affect the performance of the job service and the file size of recordings. Refer to the :ref:`deployment section <administration-guide/configure/calls-deployment:call recording and transcription>` for more information.
- The quality setting will affect the performance of the job service and the file size of recordings. Refer to the :doc:`Calls deployment guide </administration-guide/configure/calls-deployment-guide>` documentation for more information.

.. config:setting:: enable-pluginscalltranscriptions
:displayname: Enable call transcriptions (Plugins - Calls)
Expand Down Expand Up @@ -810,7 +810,7 @@ Transcriber model size

.. note::
- This setting is applicable only to self-hosted deployments.
- This setting is available starting in plugin version 0.22. The model size setting will affect the performance of the job service. Refer to the :ref:`configure call recordings, transcriptions, and live captions <administration-guide/configure/calls-deployment:call recording and transcription>` documentation for more information.
- This setting is available starting in plugin version 0.22. The model size setting will affect the performance of the job service. Refer to the :doc:`Calls deployment guide </administration-guide/configure/calls-deployment-guide>` documentation for more information.

.. config:setting:: call-transcriber-threads
:displayname: Call transcriber threads (Plugins - Calls)
Expand All @@ -834,7 +834,7 @@ Call transcriber threads

.. note::
- This setting is applicable only to self-hosted deployments.
- The call transcriber threads setting will affect the performance of the job service. Refer to the :ref:`configure call recordings, transcriptions, and live captions <administration-guide/configure/calls-deployment:call recording and transcription>` documentation for more information. This setting is available starting in plugin version 0.26.2.
- The call transcriber threads setting will affect the performance of the job service. Refer to the :doc:`Calls deployment guide </administration-guide/configure/calls-deployment-guide>` documentation for more information. This setting is available starting in plugin version 0.26.2.

.. config:setting:: enable-pluginslivecaptions
:displayname: (Experimental) Enable live captions (Plugins - Calls)
Expand Down
2 changes: 1 addition & 1 deletion source/conf.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -423,7 +423,7 @@ def setup(app: Sphinx):

sphinx_tabs_disable_tab_closing = True
sphinx_tabs_disable_css_loading = False
myst_enable_extensions = ["colon_fence"]
myst_enable_extensions = ["colon_fence", "tasklist"]
myst_heading_anchors = 3

# Suppress particular classes of warnings
Expand Down
3 changes: 2 additions & 1 deletion source/deployment-guide/deployment-guide-index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,15 @@ Whether you're deploying the server application, desktop application, or mobile
Quick Start Evaluation </deployment-guide/quick-start-evaluation>
Reference Architecture </deployment-guide/reference-architecture/reference-architecture-index>
Server Deployment </deployment-guide/server/server-deployment-planning>
Calls Deployment </administration-guide/configure/calls-deployment-guide>
Desktop App Deployment </deployment-guide/desktop/desktop-app-deployment>
Mobile App Deployment </deployment-guide/mobile/mobile-app-deployment>
Deployment Troubleshooting </deployment-guide/deployment-troubleshooting>


* :doc:`Quick Start Evaluation </deployment-guide/quick-start-evaluation>` - A quick start guide to help you get started with Mattermost.
* :doc:`Reference Architecture </deployment-guide/reference-architecture/reference-architecture-index>` - Reference architectures for scaling Mattermost and specialized deployment scenarios.
* :doc:`Server deployment </deployment-guide/server/server-deployment-planning>` - Pre-deployment checks, security considerations, hardware recommendations, software prerequisites, and step-by-step guidance to deploying Mattermost server.
* :doc:`Calls Deployment Guide </administration-guide/configure/calls-deployment-guide>` - Deploy and operate Mattermost Calls infrastructure, including RTCD, recording services, and supporting network configuration.
* :doc:`Desktop deployment </deployment-guide/desktop/desktop-app-deployment>` - Installation procedures for Mattermost's desktop applications across Windows, macOS, and Linux, and large-scale, enterprise-wide deployments.
* :doc:`Mobile deployment </deployment-guide/mobile/mobile-app-deployment>` - How to set up push notifications using Mattermost's notification service and troubleshooting tips.
* :doc:`Deployment troubleshooting </deployment-guide/deployment-troubleshooting>` - Best practices for diagnosing and resolving common deployment issues.
Expand Down
6 changes: 3 additions & 3 deletions ...ent-guide/reference-architecture/deployment-scenarios/air-gapped-deployment.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ On an internet connected machine, you must gather all required packages, contain
**(Optional) Supporting Services**
Consider downloading these additional resources if you plan to enable these optional components:

- :doc:`Mattermost Calls </administration-guide/configure/calls-deployment>`: `mattermost-calls-offloader <https://github.com/mattermost/calls-offloader/releases>`__ (required for recording, transcription and live captions) and `mattermost-rtcd <https://github.com/mattermost/rtcd/releases>`__ (required for performance and scalability).
- :doc:`Mattermost Calls </administration-guide/configure/calls-deployment-guide>`: `mattermost-calls-offloader <https://github.com/mattermost/calls-offloader/releases>`__ (required for recording, transcription and live captions) and `mattermost-rtcd <https://github.com/mattermost/rtcd/releases>`__ (required for performance and scalability).
- `Elasticsearch <https://www.elastic.co/downloads/elasticsearch>`__ can be `deployed <https://www.elastic.co/docs/deploy-manage/deploy/self-managed/installing-elasticsearch>`__ for enhanced search performance at scale.
- `Prometheus <https://prometheus.io/download/>`_ and `Grafana <https://grafana.com/grafana/download>`__ for monitoring and observability

Expand All @@ -79,7 +79,7 @@ On an internet connected machine, you must gather all required packages, contain
**(Optional) Supporting Services**
Consider downloading these additional resources if you plan to enable these optional components:

- :doc:`Mattermost Calls </administration-guide/configure/calls-deployment>` helm charts: `mattermost-calls-offloader <https://github.com/mattermost/mattermost-helm/tree/master/charts/mattermost-calls-offloader>`__ and `values <https://github.com/mattermost/mattermost-helm/blob/master/charts/mattermost-calls-offloader/values.yaml>`__ (required for recording, transcription and live captions), `mattermost-rtcd <https://github.com/mattermost/mattermost-helm/tree/master/charts/mattermost-rtcd>`__ and `values <https://github.com/mattermost/mattermost-helm/blob/master/charts/mattermost-rtcd/values.yaml>`__ (required for performance and scalability).
- :doc:`Mattermost Calls </administration-guide/configure/calls-deployment-guide>` helm charts: `mattermost-calls-offloader <https://github.com/mattermost/mattermost-helm/tree/master/charts/mattermost-calls-offloader>`__ and `values <https://github.com/mattermost/mattermost-helm/blob/master/charts/mattermost-calls-offloader/values.yaml>`__ (required for recording, transcription and live captions), `mattermost-rtcd <https://github.com/mattermost/mattermost-helm/tree/master/charts/mattermost-rtcd>`__ and `values <https://github.com/mattermost/mattermost-helm/blob/master/charts/mattermost-rtcd/values.yaml>`__ (required for performance and scalability).
- `Elasticsearch <https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s>`__ can be `deployed in air-gapped k8 environments <https://www.elastic.co/guide/en/cloud-on-k8s/2.8/k8s-air-gapped.html>`__ for enhanced search performance at scale.
- `Prometheus <https://github.com/prometheus-operator/prometheus-operator>`__ and `Grafana <https://github.com/grafana/grafana-operator>`__ operators for monitoring and observability

Expand All @@ -97,7 +97,7 @@ On an internet connected machine, you must gather all required packages, contain
**(Optional) Supporting Services**
Consider downloading these additional resources if you plan to enable these optional components:

- :doc:`Mattermost Calls </administration-guide/configure/calls-deployment>` images: `calls-offloader <https://hub.docker.com/r/mattermost/calls-offloader>`__ (required for recording, transcription and live captions) and `rtcd <https://hub.docker.com/r/mattermost/rtcd>`__ (required for performance and scalability).
- :doc:`Mattermost Calls </administration-guide/configure/calls-deployment-guide>` images: `calls-offloader <https://hub.docker.com/r/mattermost/calls-offloader>`__ (required for recording, transcription and live captions) and `rtcd <https://hub.docker.com/r/mattermost/rtcd>`__ (required for performance and scalability).
- `Elasticsearch <https://hub.docker.com/_/elasticsearch>`__ image for enhanced search performance at scale.
- `Prometheus <https://hub.docker.com/r/prom/prometheus>`__ and `Grafana <https://hub.docker.com/r/grafana/grafana>`__ images for monitoring and observability.

Expand Down
Loading
Loading