-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix securityContext for Knative Service Pod (user-container and queue-proxy) #14363
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
Conversation
|
Skipping CI for Draft Pull Request. |
11c7925 to
58a7ebc
Compare
|
To confirm - Does the changes in this PR imply that |
58a7ebc to
72613d2
Compare
yeah, that is what I'm seeing. This issue (#14365) has an example of the errors I see on my deployment |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #14363 +/- ##
==========================================
+ Coverage 86.12% 86.15% +0.02%
==========================================
Files 196 196
Lines 14787 14790 +3
==========================================
+ Hits 12735 12742 +7
+ Misses 1744 1743 -1
+ Partials 308 305 -3
☔ View full report in Codecov by Sentry. |
|
/lgtm |
|
@dprotaso: once the present PR merges, I will cherry-pick it on top of release-1.11 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, KauzClay 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 |
|
/cherry-pick release-1.10 |
|
@dprotaso: once the present PR merges, I will cherry-pick it on top of release-1.10 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@dprotaso: new pull request created: #14377 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@dprotaso: new pull request created: #14378 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Woohoo! This is a good change |
|
Surprisingly it means no one has used the secure-pod-defaults feature on a restricted profile :/ |
…-proxy) (knative#14363) * add seccompProfile to queue container security context * run as non root by default * update tests to expect new default run as nonroot
The pull request is needed to force Knative to set runAsNonRoot when secure-pod-defaults is true. The option forces knative to create the user pods with all the safest security options to pass the PSS restriction policy, but at the moment it is lacking runAsNonRoot forced to true. Note: I haven't backported the whole patch since part of it overlapped with a previous one for queue.go, where seccomp's defaults were set. The same code was committed in different pull requests, so I just removed the bit already there to allow patch to avoid error/warnings. Bug: T369493 Change-Id: Iceb1ac2d83f298ef2a834e24a8fdc8a6f1df4a28
Fixes #14365
Related to:
Proposed Changes
secure-pod-defaults, I still get errors.Release Note