-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
[Pod Security] Restricted volume type check #103323
[Pod Security] Restricted volume type check #103323
Conversation
@sejr: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
Hi @sejr. Thanks for your PR. I'm waiting for a kubernetes 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. |
a327915
to
0ce0346
Compare
0ce0346
to
b089e19
Compare
/ok-to-test |
staging/src/k8s.io/pod-security-admission/policy/check_restrictedVolumes.go
Show resolved
Hide resolved
staging/src/k8s.io/pod-security-admission/policy/check_restrictedVolumes.go
Show resolved
Hide resolved
staging/src/k8s.io/pod-security-admission/test/fixtures_restrictedVolumes.go
Outdated
Show resolved
Hide resolved
staging/src/k8s.io/pod-security-admission/test/fixtures_restrictedVolumes.go
Outdated
Show resolved
Hide resolved
staging/src/k8s.io/pod-security-admission/test/fixtures_restrictedVolumes.go
Outdated
Show resolved
Hide resolved
staging/src/k8s.io/pod-security-admission/policy/check_restrictedVolumes.go
Show resolved
Hide resolved
staging/src/k8s.io/pod-security-admission/test/fixtures_restrictedVolumes.go
Outdated
Show resolved
Hide resolved
staging/src/k8s.io/pod-security-admission/test/fixtures_restrictedVolumes.go
Outdated
Show resolved
Hide resolved
}, | ||
}, | ||
}, | ||
} |
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.
add a CSI volume to the set of volumes in the pass testcase
add a TODO to add an Ephemeral volume to the set of volumes in the pass testcase once the Ephemeral feature graduates
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.
oh, the inline CSI volume source requires the CSIInlineVolume feature gate... I hadn't realized that hadn't graduated yet. Drop this from the pass fixture and add a TODO to add it back once the CSIInlineVolume feature graduates to GA
staging/src/k8s.io/pod-security-admission/policy/check_restrictedVolumes.go
Show resolved
Hide resolved
b089e19
to
f5e9c14
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, sejr 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 |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
/hold the CSI volume in the "pass" fixture is not valid:
|
f5e9c14
to
6335a9f
Compare
podsecurity: restricted volumes check
6335a9f
to
13a1804
Compare
/lgtm |
/retest |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds a restricted policy check for volume types.
Which issue(s) this PR fixes:
Fixes #103203
Special notes for your reviewer:
If it doesn't already exist, I'm very tempted to add some kind of test utility functions for generating valid specs for these platform-specific volume types that have differing validation requirements.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig auth security