本页面为机器翻译。阅读英文原文。

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.

来源

官方由本目录认定为官方发布者的签名身份签名。
内容摘要
sha256:e41f9b088537b784dcc0eb6a73aad4c07fe9d4687d4567426a235b104907b83a
发布时间
2026-11-10T10:12:26Z
签名身份
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

签名

  • 官方application/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

此版本的引用

oci://hub.aggrega.ai/component/core/messaging/livekit-server:1.0.0

开发者参数

开发者在 Aggregate 中设置的值。

名称类型默认值必需描述
api_keystringdevkey否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_enabledbooleanfalse否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.

运维规格

运维人员按环境调整的基础设施规格。

名称类型默认值必需描述
portinteger (min 1024, max 65535)7880否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_portinteger (min 1024, max 65535)7881否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_portinteger (min 1024, max 65535)7882否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_startinteger (min 1024, max 65535)—否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_endinteger (min 1024, max 65535)—否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_versionstringv1.13.6否Server container image tag. Selects the image tag on container targets.
log_levelstring (debug | info | warn | error)info否Server log verbosity.
computeobject—否—
overridesobject (open)—否Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

输出契约

此组件通过 uses 拓扑向使用方发布的值。

名称类型默认值必需描述
hoststring—是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.
portinteger—是TCP port that Service accepts signalling and API requests on. It carries the signalling port an operator set, never one of the media ports.
protocolstring—否How the published address is spoken to — `ws`, since a client opens a WebSocket signalling session before any media flows.
api_keystring—否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_endpointstring—否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.

uses 套接字

此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。

state_store

选择器
component.aggrega.ai/category=datastore
注入
env

经由此套接字的每个连接可填充的槽位

槽位选择器必需注入敏感描述
server_cafeature.aggrega.ai/kind=secret否file是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.

附加槽位

Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。

槽位选择器必需注入敏感描述
api_secretfeature.aggrega.ai/kind=secret是env是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.

自注入允许列表

env

关系

与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。

使用

被使用

Component 概念参考 →

Aggrega 目录 — 收录组件、功能、配方以及渲染它们的插件的开放索引。

基于共享的 Aggrega 设计系统构建。

隐私