fix: add NetworkPolicy workaround for nvsentinel metrics-access restriction#68
Merged
mchmarny merged 3 commits intoNVIDIA:mainfrom Feb 6, 2026
Merged
Conversation
…iction NVSentinel (< v0.7.0) creates a "metrics-access" NetworkPolicy that restricts ingress to only metrics ports (2112/9216), blocking traffic needed by other components in the namespace — notably DCGM (port 5555) and cert-manager webhook (port 443). This adds an additive NetworkPolicy allowing all intra-namespace pod-to-pod ingress to neutralize the restriction. Upstream fix: NVIDIA/NVSentinel#789 Remove allow-intra-namespace.yaml once nvsentinel includes the networkPolicy.enabled flag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Coverage Report ✅
Coverage BadgeCoverage unchanged by this PR. |
lalitadithya
approved these changes
Feb 6, 2026
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
3 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.
Summary
allow-intra-namespaceNetworkPolicy to neutralize the overly restrictivemetrics-accessNetworkPolicy created by NVSentinel (< v0.7.0)metrics-accesspolicy restricts ingress to only ports 2112/9216, blocking traffic needed by other components in the namespace (e.g. DCGM port 5555, cert-manager webhook port 443)Problem
When deployed in a shared namespace, the nvsentinel
metrics-accessNetworkPolicy blocks:dcgm-exportercannot connect → panic → CrashLoopBackOffstartupapicheckfails with connection timeoutChanges
pkg/recipe/data/components/nvsentinel/manifests/allow-intra-namespace.yamlpkg/recipe/data/overlays/base.yaml— addedmanifestFilesreference to nvsentinel componentUpstream fix
NVIDIA/NVSentinel#789 (merged) adds a
networkPolicy.enabledflag. This workaround should be removed once we pick up the nvsentinel chart version that includes it.Test plan
go test ./pkg/recipe/... ./pkg/bundler/...— all passeidos recipe + eidos bundle— generates bundle withallow-intra-namespace.yamlin templates/helm template— renders valid NetworkPolicy🤖 Generated with Claude Code