From 77c3a92f20152beb710163c61f2df70ae63768f6 Mon Sep 17 00:00:00 2001 From: Kornel David Date: Tue, 15 Oct 2024 21:30:08 +0200 Subject: [PATCH] docs(/examples/mediasoup): Add missing mediasoup arch fig --- docs/examples/mediasoup/README.md | 2 ++ docs/img/stunner_mediasoup.svg | 4 ++++ 2 files changed, 6 insertions(+) create mode 100644 docs/img/stunner_mediasoup.svg diff --git a/docs/examples/mediasoup/README.md b/docs/examples/mediasoup/README.md index 675947d..d9815f0 100644 --- a/docs/examples/mediasoup/README.md +++ b/docs/examples/mediasoup/README.md @@ -24,6 +24,8 @@ The recommended way to install mediasoup ([link](https://mediasoup.discourse.gro The figure below shows mediasoup deployed into regular Kubernetes pods behind STUNner without the host-networking hack. Here, mediasoup is deployed behind STUNner in the [*media-plane deployment model*](../../DEPLOYMENT.md), so that STUNner acts as a "local" STUN/TURN server for mediasoup, saving the overhead of using public a 3rd party STUN/TURN server for NAT traversal. +![STUNner mediasoup integration deployment architecture](../../img/stunner_mediasoup.svg) + In this tutorial we deploy a video room example using [mediasoup's demo application](https://github.com/versatica/mediasoup-demo/) with slight modifications (more on these below), the [mediasoup server](https://github.com/versatica/mediasoup/) for media exchange, a Kubernetes Ingress gateway to secure signaling connections and handle TLS, and STUNner as a media gateway to expose the mediasoup server pool to clients. ### Modifications on the mediasoup demo diff --git a/docs/img/stunner_mediasoup.svg b/docs/img/stunner_mediasoup.svg new file mode 100644 index 0000000..5949b7b --- /dev/null +++ b/docs/img/stunner_mediasoup.svg @@ -0,0 +1,4 @@ + + + +
Kubernetes  cluster
Kubernetes  cluster
HTTPS
HTTPS
Ingress
Ingress
UDP/RTP
UDP/RTP
STUN/TURN
STUN/TURN
\ No newline at end of file