Skip to content

[v1.19] fix: add podSecurityLabelSync=true to openshift-gitops (#1105)#1121

Open
nmirasch wants to merge 1 commit intoredhat-developer:v1.19from
nmirasch:GITOPS-9158_add_podSecurityLabelSync_v1.19
Open

[v1.19] fix: add podSecurityLabelSync=true to openshift-gitops (#1105)#1121
nmirasch wants to merge 1 commit intoredhat-developer:v1.19from
nmirasch:GITOPS-9158_add_podSecurityLabelSync_v1.19

Conversation

@nmirasch
Copy link
Copy Markdown
Contributor

@nmirasch nmirasch commented Apr 9, 2026

  • fix: add podSecurityLabelSync=true to openshift-gitops

  • e2e check at least one PSS label is set by Openshift

  • assert podSecurityLabelSync and audit=restricted for openshift-gitops ns

  • added podSecurityLabels validation for enforce, warn and *-version presence


(cherry picked from commit 88b2301)

…per#1105)

* fix: add podSecurityLabelSync=true to openshift-gitops

Signed-off-by: nmirasch <neus.miras@gmail.com>

* e2e check at least one PSS label is set by Openshift

Signed-off-by: nmirasch <neus.miras@gmail.com>

* assert podSecurityLabelSync and audit=restricted for openshift-gitops ns

Signed-off-by: nmirasch <neus.miras@gmail.com>

* added podSecurityLabels validation for enforce, warn and *-version presence

Signed-off-by: nmirasch <neus.miras@gmail.com>

---------

Signed-off-by: nmirasch <neus.miras@gmail.com>
(cherry picked from commit 88b2301)
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 9, 2026

Hi @nmirasch. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

@svghadi
Copy link
Copy Markdown
Member

svghadi commented Apr 9, 2026

/ok-to-test
/lgtm
/approve

@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: svghadi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Apr 9, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 9, 2026

@nmirasch: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/v4.19-e2e a5e32a9 link true /test v4.19-e2e
ci/prow/v4.19-kuttl-parallel a5e32a9 link true /test v4.19-kuttl-parallel

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@nmirasch
Copy link
Copy Markdown
Contributor Author

/retest

@jgwest
Copy link
Copy Markdown
Member

jgwest commented Apr 10, 2026

cluster flake /retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants