Component
core/messaging/livekit-server
A LiveKit media server — the selective forwarding unit that carries realtime audio and video between the participants of a room. A client opens a WebSocket signalling session on the API port, then exchanges media over WebRTC, which the server terminates either on one multiplexed UDP port with a TCP port beside it as the fallback path for clients whose network blocks UDP, or on a contiguous range of UDP ports that gives each connection its own socket, which carries traffic only where the pod uses the node's own network. Wire here when the cluster carries realtime voice or video itself rather than handing the media to a carrier it does not run, and the same server serves conventional applications as readily as agent workloads. Consumers receive the server's in-cluster host, its signalling port, the protocol that port speaks, and the API key identifier they pair with their own issued secret; the token-signing secret arrives through the api_secret slot here and as the `credential` on each consumer's connection to this server, and is never published on the topology. Realized by a Helm Recipe that synthesizes a Deployment and a ClusterIP Service over the upstream image and declares no volume: the server holds no durable disk, keeping room and participant state in memory, so more than one replica means wiring the state-store socket to a Redis-compatible datastore rather than adding storage here. With `values.metrics_enabled` true the Recipe turns on the server's metrics, on a port of their own that checks no caller, and publishes their address as `metrics_endpoint`; false, that key is empty.
Provenienza
- Digest del contenuto
- sha256:e41f9b088537b784dcc0eb6a73aad4c07fe9d4687d4567426a235b104907b83a
- Pubblicato
- 2026-11-10T10:12:26Z
- Identità di firma
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Firma
- Ufficialeapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:cac242eca02a697ec799a2664609dc0c5931199d11ed30bcbd5f9a486c070a0d
Riferimento a questa versione
oci://hub.aggrega.ai/component/core/messaging/livekit-server:1.0.0Parametri dello sviluppatore
Valori che lo sviluppatore imposta nell’Aggregate.
| Nome | Tipo | Predefinito | Obbligatorio | Descrizione |
|---|---|---|---|---|
| api_key | string | devkey | no | Public identifier of the API key pair. It travels in the clear inside every access token the server issues, so it is not secret; the secret half is the api_secret credential slot. |
| metrics_enabled | boolean | false | no | Turns on the server's own metrics, in the Prometheus format, on a port of their own, 6789, and publishes their address as `metrics_endpoint`; while false that key is empty. The metrics port checks no caller, so anything that reaches it can read them. |
Dimensionamento dell’operatore
Dimensionamento dell’infrastruttura che l’operatore regola per ogni ambiente.
| Nome | Tipo | Predefinito | Obbligatorio | Descrizione |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 7880 | no | Signalling and API port. Clients open their WebSocket session here and the server APIs answer on it. Most operators should omit this and let the Recipe assign the default (7880). |
| rtc_tcp_port | integer (min 1024, max 65535) | 7881 | no | TCP port carrying WebRTC media for clients whose network blocks UDP. It is a fallback path rather than the ordinary one, and it stays declared so such a client still connects. |
| rtc_udp_port | integer (min 1024, max 65535) | 7882 | no | Single UDP port all WebRTC media is multiplexed onto. It is declared as a container port and fronted by the Service, so it is the media path a Release reaches with no further host configuration. It carries the media while the two range bounds below are unset; setting both of them selects the range instead, and this port is then neither configured nor declared. |
| rtc_port_range_start | integer (min 1024, max 65535) | — | no | First port of the contiguous UDP range the server draws a per-connection media port from. Set it together with rtc_port_range_end — the server reads the range only when both bounds are present, and carries media on the multiplexed rtc_udp_port when either is missing. A range gives each connection its own socket rather than multiplexing every connection onto one, which raises the media throughput a single server sustains. The ports in it are configuration the server reads rather than ports the component declares — they are not container ports and no Service fronts them, so they carry client traffic only where the pod uses the node's own network and the range is open on the node's firewall. |
| rtc_port_range_end | integer (min 1024, max 65535) | — | no | Last port of the contiguous UDP media range, inclusive, and greater than rtc_port_range_start. Set it together with rtc_port_range_start — the server reads the range only when both bounds are present. |
| engine_version | string | v1.13.6 | no | Server container image tag. Selects the image tag on container targets. |
| log_level | string (debug | info | warn | error) | info | no | Server log verbosity. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Contratto di output
Valori che questo componente pubblica verso i consumatori attraverso la topologia uses.
| Nome | Tipo | Predefinito | Obbligatorio | Descrizione |
|---|---|---|---|---|
| host | string | — | sì | In-cluster DNS name of the Service carrying signalling. A client opens its session against this name together with `port`; the media ports are a separate path and are not published here. |
| port | integer | — | sì | TCP port that Service accepts signalling and API requests on. It carries the signalling port an operator set, never one of the media ports. |
| protocol | string | — | no | How the published address is spoken to — `ws`, since a client opens a WebSocket signalling session before any media flows. |
| api_key | string | — | no | Public identifier of the API key pair, which a consumer sends when it mints an access token. It is the naming half of the pair; the secret half arrives through the credential attached to the component's api_secret slot, and a consumer presents the same secret as `credential` on the connection that reaches this server. |
| metrics_endpoint | string | — | no | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:6789/metrics`. Empty while values.metrics_enabled is false. |
Socket uses
I socket di dipendenza attraverso cui questo componente si connette. La destinazione di ogni connessione collegata attraverso un socket deve soddisfare il suo selettore di etichette, e ogni connessione può portare un aggancio negli slot che il socket dichiara. Uno slot obbligatorio deve essere riempito da ogni connessione che l’Aggregate o la Release collega attraverso il socket.
state_store
- Selettore
- component.aggrega.ai/category=datastore
- Iniezione
- env
Slot che ogni connessione attraverso questo socket può riempire
| Slot | Selettore | Obbligatorio | Iniezione | Sensibile | Descrizione |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | no | file | sì | Optional authority the server checks the store's certificate against while the store publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and names the file in the server's store settings. The build halts on a server_ca publishing no Secret name, and on one wired to a store served without TLS. Fill it with core/referenced-secret. |
Slot di aggancio
Punti di associazione con nome in cui una Feature si aggancia a questo componente. Il selettore di uno slot limita quale Feature può riempirlo e la sua lista inject indica come può essere consegnato il materiale della Feature. Uno slot obbligatorio deve essere associato su ogni istanza, da un aggancio sull’istanza o a un ambito superiore, e uno slot sensibile è dichiarato per gestire materiale segreto. Una Feature può anche agganciarsi con un nome che nessuno slot dichiara.
| Slot | Selettore | Obbligatorio | Iniezione | Sensibile | Descrizione |
|---|---|---|---|---|---|
| api_secret | feature.aggrega.ai/kind=secret | sì | env | sì | Signing secret paired with the api_key identifier. The server issues and validates client access tokens with it, so every client of this server holds the same pair. |
Elenco consentito di auto-iniezione
env
Relazioni
Archi tipizzati da e verso altre entità pubblicate. Un riferimento senza una destinazione pubblicata viene mostrato come arco interrotto anziché come link.
Usa
- usausa il socket «state_store»
component.aggrega.ai/category=datastore
Slot di aggancio: server_ca
core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/mariadb-operator v1.0.0 →core/datastore/memcached v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/mysql-operator v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/redis v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/valkey v1.0.0 →core/datastore/weaviate v1.0.0 →
Usato da
usa il socket «media_server»
usa il socket «target_messaging»
usa il socket «upstream»
usa il socket «media_server»
usa il socket «forward_target»
usa il socket «scrape_target»
usa il socket «store»
si applica a
si applica a
si applica a
si applica a
si applica a
si applica a
si applica a
implementa