OCPBUGS-1666: Expose flag to enable/disable PodSecurity#6062
Merged
Conversation
41fd64f to
910d990
Compare
Member
Author
|
Fixes a few issues upstream and downstream: |
Member
Author
|
If you pass in an unsupported option you get the help message: |
Member
Author
|
When restricted is enabled, the pod will have the seccompProfile set on it. |
Member
Author
|
if legacy is enabled then no seccompprofile is added to the Pod. |
grokspawn
reviewed
Oct 7, 2022
grokspawn
reviewed
Oct 7, 2022
grokspawn
reviewed
Oct 7, 2022
everettraven
requested changes
Oct 7, 2022
everettraven
left a comment
Contributor
There was a problem hiding this comment.
Just a teeny nit on the changelog. Also need to run make generate to update the CLI docs with the latest changes.
grokspawn
reviewed
Oct 7, 2022
Added --security-context-config flag to enable seccompprofile. It defaults to enabled to support k8s 1.25. You can disable it with --security-context-config=legacy Signed-off-by: jesus m. rodriguez <jesusr@redhat.com>
* Ignoring error from Set call in test * Update .cncf maintainers * Update run bundle(-upgrade) CLI docs Signed-off-by: jesus m. rodriguez <jmrodri@gmail.com>
This was being duplicated because we had it in the text but were not setting the value to a default value. Once we set the value to the default cobra realized this and would output "(default: restricted)". So removing the manually entered text fixes the duplicate. Signed-off-by: jesus m. rodriguez <jesusr@redhat.com>
662a486 to
e67aa04
Compare
grokspawn
approved these changes
Oct 12, 2022
Member
Author
|
/cherry-pick v1.24.x |
|
@jmrodri: new pull request created: #6080 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. |
tiraboschi
added a commit
to tiraboschi/release
that referenced
this pull request
Jul 11, 2023
…text Add a parameter to let the users specify a value for --security-context-config (legacy/restricted, default restricted) to by used by the operator-sdk for its catalog pod. See: operator-framework/operator-sdk#6062 Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
openshift-merge-robot
pushed a commit
to openshift/release
that referenced
this pull request
Jul 11, 2023
…text (#41134) Add a parameter to let the users specify a value for --security-context-config (legacy/restricted, default restricted) to by used by the operator-sdk for its catalog pod. See: operator-framework/operator-sdk#6062 Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
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
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:
Added --security-context-config flag to enable seccompprofile. It defaults to enabled to support k8s 1.25. You can disable it with --security-context-config=legacy
Signed-off-by: jesus m. rodriguez jesusr@redhat.com
Motivation for the change:
In k8s 1.25 PodSecurityAdmission is enabled. https://kubernetes.io/blog/2022/08/04/upcoming-changes-in-kubernetes-1-25/#podsecuritypolicy-removal
Fixes a few issues found downstream but affect upstream as well:
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments(seechangelog/fragments/00-template.yaml)website/content/en/docs