Repository navigation
fix(trivy): ignore KSV-0118 for the eUPF deployment template - #655
Merged
Merged
Conversation
The config scan (enabled again in #653) fails with exit code 1 on AVD-KSV-0118 'Default security context configured' in .deploy/helm/eupf/templates/deployment.yaml. Running eUPF in a restricted security context is not supported by design: the eBPF data plane needs a privileged (root) container to load its programs, mount bpffs/debugfs and raise RLIMIT_MEMLOCK (see the chart README). Add the rule to .trivyignore with the justification instead of weakening the deployment. Verified locally: trivy fs --scanners misconfig --severity HIGH,CRITICAL with this .trivyignore and trivy.yaml reports 0 findings. Signed-off-by: pirog-spb <[email protected]>
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.
The config scan (enabled again in #653) fails with exit code 1 on AVD-KSV-0118 'Default security context configured' in .deploy/helm/eupf/templates/deployment.yaml.
Running eUPF in a restricted security context is not supported by design: the eBPF data plane needs a privileged (root) container to load its programs, mount bpffs/debugfs and raise RLIMIT_MEMLOCK (see the chart README). Add the rule to .trivyignore with the justification instead of weakening the deployment.
Verified locally: trivy fs --scanners misconfig --severity HIGH,CRITICAL with this .trivyignore and trivy.yaml reports 0 findings.