-
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
Update pods validation based on uniqueness of controller #106097
Merged
k8s-ci-robot
merged 2 commits into
kubernetes:master
from
liggitt:feature/pod-security/unique-controller-pods-validation
Nov 2, 2021
Merged
Update pods validation based on uniqueness of controller #106097
k8s-ci-robot
merged 2 commits into
kubernetes:master
from
liggitt:feature/pod-security/unique-controller-pods-validation
Nov 2, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt 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 |
/assign @enj |
/lgtm |
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
kind/feature
Categorizes issue or PR as related to a new feature.
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
release-note-none
Denotes a PR that doesn't merit a release note.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Builds on #104420 from @akshitgrover (keeping author attribution), adding unit tests and addressing review comments
original description from #104420 follows:
Signed-off-by: Akshit Grover [email protected]
What type of PR is this?
/kind feature
What this PR does / why we need it:
Updates namespaced pod evaluation logic of PodSecurity controller to prioritize evaluation of pods based on uniqueness of the controller that pod belongs to
Which issue(s) this PR fixes:
Fixes #103304
Special notes for your reviewer:
We might need to add some unit tests to validate this scenario but before that I'll need some inputs on the clean way of adding one as it's not straightforward to add a unit test for this scenario, Or if there are any other types of test category we should use
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: