Configure test pod to comply with Pod Security Standard#6181
Closed
bcrochet wants to merge 1 commit into
Closed
Conversation
acornett21
approved these changes
Nov 15, 2022
Contributor
Author
|
/retest |
|
@bcrochet: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn 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. |
The test pod is not yet created in accordance with the Pod Security
Standard enforced in k8s 1.24. For compliance, the main pod security
context needs:
RunAsNonRoot: true
SeccompProfile:
Type: RuntimeDefault
And each container needs:
SecurityContext:
AllowPrivilegeEscalation: false
Capabilities:
Drop:
'ALL'
Fixes operator-framework#5939
Signed-off-by: Brad P. Crochet <brad@redhat.com>
Member
Contributor
|
/ok-to-test |
Contributor
Author
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description of the change:
The test pod is not yet created in accordance with the Pod Security Standard enforced in k8s 1.24. For compliance, the main pod security context needs:
RunAsNonRoot: true
SeccompProfile:
Type: RuntimeDefault
And each container needs:
SecurityContext:
AllowPrivilegeEscalation: false
Capabilities:
Drop:
'ALL'
Fixes #5939
Signed-off-by: Brad P. Crochet brad@redhat.com
Motivation for the change:
Scorecard tests would not run under k8s 1.24 or OpenShift 4.12. This re-enables that functionality.
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments(seechangelog/fragments/00-template.yaml)website/content/en/docs