-
Notifications
You must be signed in to change notification settings - Fork 76
refactor(nvsnap): remove the LD_PRELOAD interception stack criu-v2 replaced #2097
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
balajinvda
wants to merge
3
commits into
main
Choose a base branch
from
nvsnap/remove-injection-stack
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
2afb549
refactor(nvsnap): remove the LD_PRELOAD interception stack criu-v2 re…
balajinvda c49254b
refactor(nvsnap): finish removing the interception stack from build a…
balajinvda 88a6be8
fix(nvsnap): make the validate-test-env build hint build the expected…
balajinvda File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: NVIDIA/nvcf
Length of output: 23699
🏁 Script executed:
Repository: NVIDIA/nvcf
Length of output: 28265
Confirm migration for separately configured auto-injection deployments.
The base Helm chart passes the four image references as positional arguments, but the agent declares them as
--webhook-image-*flags. Normal chart deployment therefore leavesconfig.Webhook.AutoInjectempty, so annotated pods do not receive auto-injection. Separately configured agents that pass these flags can still serve the documentednvsnap.io/auto-injectcontract.Before removing this path, confirm that those customer or BYOC deployments and workloads are migrated.
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed on the distinction, and it is a fair correction to how I worded the PR.
The claim that holds is narrower than "non-functional": it is non-functional for
any deployment produced by this repository. An agent started by hand with the
four
--webhook-image-*flags set would serve the annotation contract.What I can verify here, I have:
webhook-image-on main are the fourflag.StringVardeclarationsthemselves. The chart and both DaemonSet manifests pass the images as bare
positional arguments, and nothing reads
flag.Args().nvsnap.io/auto-injectappears nowhere indocs/orfern/, so it is not adocumented public surface, and nothing outside the nvsnap subtree references
it.
What I cannot verify from here is whether some out-of-band deployment sets the
flags explicitly. That confirmation is already requested in the PR description
and is the one open item on this change. Worth noting the failure mode if such a
deployment does exist: removal makes the annotation silently inert rather than an
error, so the pod would start without the injected stack instead of failing
loudly. If that risk is judged material, the cheap mitigation is to keep the
annotation recognised for one release and log a warning when it is set, rather
than to keep the stack.
Flagging for whoever owns BYOC onboarding rather than resolving it myself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@balajinvda, thanks for clarifying. I agree that repository-produced deployments did not activate auto-injection. The remaining concern is limited to agents configured outside this repository.The PR description identifies confirmation with BYOC onboarding as an open item. I’ll leave this thread open for that confirmation. If those deployments exist, the annotation could become silently inert after removal. A warning for one release is a reasonable mitigation if the owner judges that risk material. I am not asking to restore the image-flag wiring.
You are interacting with an AI system.