Add nvidia-vss-ingress 3.1.4 (NVIDIA VSS Blueprint 3.1.0)#244
Open
blik616287 wants to merge 6 commits into
Open
Add nvidia-vss-ingress 3.1.4 (NVIDIA VSS Blueprint 3.1.0)#244blik616287 wants to merge 6 commits into
blik616287 wants to merge 6 commits into
Conversation
There was a problem hiding this comment.
✅ CVE scan completed successfully.
Scan Summary:
- Total images scanned: 3
- Clean images: 2
- Images with CVEs: 1
- Total CVEs found: 137
🔴 Critical CVEs: 3
🟠 High CVEs: 21
🟡 Medium CVEs: 18
🟢 Low CVEs: 95
Images with CVEs:
- nginx:1.27-alpine: 137 CVEs (Critical: 3, High: 21, Medium: 18, Low: 95)
Critical CVEs: CVE-2025-48174, CVE-2026-31789
…guard vss-proxy Drop the gated nvcr envoy-proxy/vss-vios-ingress and the CVE-laden nginx:1.27-alpine (3 Crit/21 High) from pack content. content.images is now wolfi-base + chainguard/nginx (0/0). The gated envoy + vss-vios-ingress rootfs are crane-fetched as runtime DATA at deploy and run NON-PRIVILEGED on wolfi-base via the matched-ld swap; vss-proxy uses the public Chainguard nginx. GB10-validated: envoy 1.23.1/BoringSSL + nginx/1.24.0 execute under the swap. The running containers carry NVIDIA CVEs as runtime data, not pack images. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
envoy embedded luajit resolves the redis filters require to the container /usr/local (empty) without a chroot -> set LUA_PATH/LUA_CPATH at the rootfs lua dirs (redis.lua is in usr/local/share/lua/5.1). Found on the live GB10 deploy (script load error: module redis not found). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
3.1.3 validated on a GB10 edge cluster. Merged upstream/main (crane-manifest validator fix). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds the sdr (WDM) service in native Kubernetes mode (WDM_CLUSTER_TYPE=k8s + ServiceAccount/RBAC + kubernetes ExternalName), replacing the docker.sock discovery that can't run in k8s. sdr selected the k8s client, authenticated, and served xDS. Live-validated on a GB10 (DGX Spark) edge cluster via the cluster-profile pipeline. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
nvidia-vss-ingress — VSS 3.x, pack
3.1.2VSS 3.x ingress as a Helm chart —
envoy-proxy, thevss-proxy(nginx) edge router to vss-agent/UI/VST, andvss-vios-ingress. Note:sdr(the envoy xDS control-plane for live-stream routing) is deferred — its image discovers workloads via the Docker socket (WDM_CLUSTER_TYPE=docker) and has no k8s service-discovery mode; not needed for the base summarization route.Versioning: chart/pack
version: 3.1.2(our packaging) ·appVersion: 3.1.0(upstream NVIDIA VSS Blueprint 3.x). Helm chart; images pinned invalues.yamlpack.content.images.Tested on NVIDIA GB10 / DGX Spark (arm64 SBSA)
Deployed via Palette add-on cluster profile
vss-dgx-spark-3xon edge clusteredge-gx10(single GB10). Full VSS 3.x route green — all 5 packs reportPack services are ready, cluster Running:Validation:
pack.jsonJSON-syntax/schema/version, logo, README, andpack.content.imagesall pass. Thecontent.imagespull (crane) fails for the gatednvcr.io/nim/*andnvcr.io/nvidia/vss-core/*images — the CI runner has no NGC credentials (same image-pull exception as the 2.4 PRs #233–236; the cluster pulls them viangc-pull-secret).