Skip to content

.#164

Closed
nagar-decart wants to merge 1 commit into
livekit:masterfrom
nagar-decart:egress-extraenv-envfrom
Closed

.#164
nagar-decart wants to merge 1 commit into
livekit:masterfrom
nagar-decart:egress-extraenv-envfrom

Conversation

@nagar-decart

@nagar-decart nagar-decart commented Jun 30, 2026

Copy link
Copy Markdown

No description provided.

Lets operators inject extra container env vars and envFrom sources (e.g.
LIVEKIT_API_KEY / LIVEKIT_API_SECRET, or S3 credentials) from a Secret
instead of embedding them in the config ConfigMap. The egress binary already
reads LIVEKIT_API_KEY / LIVEKIT_API_SECRET / LIVEKIT_WS_URL from env as
defaults, so this enables credential-from-Secret deployments without
exposing them in the public ConfigMap.

Both default to empty lists, so existing deployments are unaffected.
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@nagar-decart nagar-decart deleted the egress-extraenv-envfrom branch June 30, 2026 12:10
@nagar-decart nagar-decart changed the title feat(egress): add extraEnv and envFrom to the egress deployment . Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants