Conversation
Bumps chart version and appVersion from v1.8.5 to v1.9.11, the latest stable release. Key changes in v1.9.11 include OpenTelemetry tracing support, force simulcast codec option, participant option for data track auto-subscribe, and a fix for the crash introduced in v1.9.10. Made-with: Cursor
Bumps chart version and appVersion from v1.8.5 to v1.10.0, the latest release (March 23, 2026). Minor version bump upstream due to logging key rename: pID -> participantID. Also includes a gRPC update addressing CVE-2026-33186. Made-with: Cursor
Update livekit server v1.10.0
Bumps chart version and appVersion from v1.8.5 to v1.9.12 (March 5, 2026). Targeting v1.9.12 rather than v1.10.0 to avoid a known bug in the v1.10 release. Made-with: Cursor
Update livekit-server to v1.9.12
Co-authored-by: Cursor <cursoragent@cursor.com>
chore: add Harbor OCI publish workflow
Co-authored-by: Cursor <cursoragent@cursor.com>
fix: escape robot account dollar sign in helm registry login
Bumps chart to v1.10.3. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
One DaemonSet and ConfigMap per LiveKit node so each SFU can advertise its own rtc.node_ip. Empty instances keeps the previous single-workload behaviour; TURN/TLS stays on the shared Service.
feat: per-node media VIP instances for the SFU
Bring in upstream chart version bumps (egress 1.12.0, ingress 1.5.0, livekit-server appVersion v1.11.0). Keep our DaemonSet, keys mount, and per-node instances. Upstream still has no DaemonSet. Co-authored-by: Cursor <cursoragent@cursor.com>
Bump chart version to 1.12.0 so Harbor publishes a new package. Default image follows current LiveKit; DaemonSet and instances stay in the fork because upstream still has neither. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Johannes Coetsee seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Author
|
Opened against the wrong repository (this is our Meedio fork sync). Closing; the real PR is on meedio/livekit-helm. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ref: https://github.com/meedio/k8s-configuration/issues/2275
Summary
livekit/livekit-helmmaster (2 commits). Upstream still has no DaemonSet — that remains the reason for this fork, plus keys-directory mount and per-nodeinstances.livekit-serverto chart 1.12.0 /appVersionv1.13.7 (latest server, 2026-09-14).Staging already pins chart
v1.11.0and will override the image separately. After merge, tag v1.12.0 so Flux can consume this chart later. Harbor will publish1.12.0from master.Test plan
livekit/livekit-helmmasterv1.12.0v1.13.7on the existingv1.11.0chart firstMade with Cursor