authentication: pod-security initial commit #899
Merged
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
This was referenced Sep 22, 2021
Merged
This was referenced Oct 1, 2021
Merged
Merged
Merged
wking
reviewed
Oct 1, 2021
bparees
reviewed
Oct 1, 2021
bparees
reviewed
Oct 1, 2021
bparees
reviewed
Oct 1, 2021
bparees
reviewed
Oct 1, 2021
s-urbaniak
force-pushed
the
podsecurity
branch
2 times, most recently
from
2823a2e
to
b9716dd
Compare
|
/approve this is in line with the plan that was debated in control plane theme call and also internally. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mfojtik 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 |
openshift-ci
bot
added
the
approved
stlaz
reviewed
Oct 4, 2021
Comment on lines
60
to
68
| 1. (DONE) Enable the PodSecurity admission plugin in no-op mode but with the ability to audit policy violations. | ||
|
|
||
| - https://github.com/openshift/api/pull/1001 add `PodSecurity` to default enabled feature set in OpenShift hyperkube | ||
| - https://github.com/openshift/cluster-kube-apiserver-operator/pull/1217 enable `PodSecurity` admission plugin and provide a default configuration | ||
| - https://github.com/openshift/kubernetes/pull/950 vendor api changes in openshift/kubernetes | ||
| - https://github.com/openshift/cluster-kube-apiserver-operator/pull/1231 enable `PodSecurity` feature gate in kube-apiserver-operator |
There was a problem hiding this comment.
I wouldn't post PRs in an enhancement and would stick with just the plan. You can xref the PRs in the comments.
There was a problem hiding this comment.
no disagreement, let's remove them then, at the same time leaving them here as a comment:
- config/v1: add PodSecurity to Default features api#1001: add
PodSecurityto default enabled feature set in OpenShift hyperkube - bindata: enable podsecurity plugin cluster-kube-apiserver-operator#1217: enable
PodSecurityadmission plugin and provide a default configuration - UPSTREAM: <drop>: bump openshift, k8s to 1.22.1 kubernetes#950: vendor api changes in openshift/kubernetes
- Enable PodSecurity admission by default cluster-kube-apiserver-operator#1231
s-urbaniak
force-pushed
the
podsecurity
branch
2 times, most recently
from
b99704d
to
da300a4
Compare
s-urbaniak
force-pushed
the
podsecurity
branch
from
da300a4
to
4eaffa6
Compare
|
/retest |
|
/lgtm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.