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
Default to sandbox Seccomp
field instead of SeccompProfilePath
#115898
Conversation
The seccomp field is the new default since a couple of releases, means we can stop using `SeccompProfilePath`. Follow-up on kubernetes#96281 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
fb436f3
to
58923c9
Compare
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.
LGTM
/lgtm |
LGTM label has been added. Git tree hash: 5b85f39559c403b1da38f89e8d84e53678ef72ee
|
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.
/lgtm
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dchen1107, fmuyassarov, saschagrunert, SergeyKanzhelev The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The seccomp field is the new default since a couple of releases, means we can stop using
SeccompProfilePath
.Which issue(s) this PR fixes:
Follow-up on #96281
Special notes for your reviewer:
Per #115719 (comment)
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: