-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Allow setting seccompProfile to enable using restricted security profile #13401
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
Allow setting seccompProfile to enable using restricted security profile #13401
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evankanderson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportBase: 86.52% // Head: 86.45% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #13401 +/- ##
==========================================
- Coverage 86.52% 86.45% -0.07%
==========================================
Files 196 196
Lines 14551 14556 +5
==========================================
- Hits 12590 12585 -5
- Misses 1662 1671 +9
- Partials 299 300 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
psschwei
left a comment
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.
One minor nit: we should also edit the features configmap to include this as one of the fields that can be set when the gate is on. Otherwise, looks good to me
psschwei
left a comment
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
…restricted security profile (#1284) * Allow setting seccompProfile to enable using restricted security profile (knative#13401) * fix features cm Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>
…restricted security profile (knative#1284) * Allow setting seccompProfile to enable using restricted security profile (knative#13401) * fix features cm Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>
…restricted security profile (#1284) (#9) * Allow setting seccompProfile to enable using restricted security profile (knative#13401) * fix features cm Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com> Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>
#91) * [RELEASE-1.5][BACKPORT] Allow setting seccompProfile to enable using restricted security profile (#1284) (#9) * Allow setting seccompProfile to enable using restricted security profile (knative#13401) * fix features cm Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com> Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com> * Update checksum Co-authored-by: Stavros Kontopoulos <st.kontopoulos@gmail.com> Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>
The commit knative/serving#13401 allows pods scheduled/created via knative-serving to be set with a seccomp profile, required by the PSS migration to allow running pods in the "restricted" security realm. The commit knative/serving#13398 adds a config-map flag to inject secure defaults for pods not running with specific settings, to allow the PSS restricted profile. Bug: T369493 Change-Id: Ib2ec22d4ccdeebda3ba775bdcd3d4e1be520f7ed
Fixes #13398
seccompProfile.typeshould only be set toRuntimeDefaultorLocalhostin therestrictedPod Security Standard.Allow users to set the
seccompProfileso that they can run Knative user-containers in restricted mode.Relates to #13376
Proposed Changes
seccompProfilein PodSecurityContext and SecurityContextRelease Note