-
Notifications
You must be signed in to change notification settings - Fork 1.2k
allow dropping securityContext capabilities #11344
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
Welcome @psschwei! It looks like this is your first PR to knative/serving 🎉 |
Hi @psschwei. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
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.
/ok-to-test
pkg/apis/serving/fieldmask.go
Outdated
// CapabilitiesMask performs a _shallow_ copy of the Kubernetes SecurityContext object to a new | ||
// Kubernetes SecurityContext object bringing over only the fields allowed in the Knative API. This | ||
// does not validate the contents or the bounds of the provided fields. |
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.
// CapabilitiesMask performs a _shallow_ copy of the Kubernetes SecurityContext object to a new | |
// Kubernetes SecurityContext object bringing over only the fields allowed in the Knative API. This | |
// does not validate the contents or the bounds of the provided fields. | |
// CapabilitiesMask performs a _shallow_ copy of the Kubernetes Capabilities object to a new | |
// Kubernetes Capabilities object bringing over only the fields allowed in the Knative API. This | |
// does not validate the contents or the bounds of the provided fields. |
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.
whoops :)
70ea252
to
84282bc
Compare
^ looks like a test flake in the new backround rate limit stuff /test pull-knative-serving-unit-tests |
Thanks for doing this! Summoning @dprotaso to gather API feedback. |
Codecov Report
@@ Coverage Diff @@
## main #11344 +/- ##
==========================================
- Coverage 87.74% 87.68% -0.07%
==========================================
Files 191 191
Lines 9215 9225 +10
==========================================
+ Hits 8086 8089 +3
- Misses 876 880 +4
- Partials 253 256 +3
Continue to review full report at Codecov.
|
@psschwei do you mind fixing the code style nits pointed out by the Github Action at https://github.com/knative/serving/pull/11344/checks?check_run_id=2598094297? |
8ee752d
to
101e01d
Compare
/retest |
/lgtm @psschwei Can we update the schemas in a follow up PR? @markusthoemmes are there docs describing how it should be done via tooling? ie. serving/config/core/300-resources/service.yaml Lines 408 to 419 in d9da69e
Similar changes should appear in the Configuration & Revision |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso 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 |
There are no docs for this just yet. It's on my TODO to make this more collaborator friendly. |
Fixes #10812 (part 1)
Proposed Changes
This fix allows dropping security context capabilities from a container via
containers[].securityContext.capabilities.drop
Release Note