Skip to content

[release-4.20] USHIFT-6156: Enable fips support for release scenarios#5592

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
kasturinarra:local-4.20
Oct 10, 2025
Merged

[release-4.20] USHIFT-6156: Enable fips support for release scenarios#5592
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
kasturinarra:local-4.20

Conversation

@kasturinarra
Copy link
Contributor

@kasturinarra kasturinarra commented Oct 9, 2025

Which issue(s) this PR addresses: Manual cherry pick of #5513 & #5588 to 4.20 branch

Closes #

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025 •
edited by openshift-ci bot
Loading

@kasturinarra: This pull request references USHIFT-6156 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses: Manual cherry pick of #5513 & #5588 to 4.20 branch

Closes #

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from agullon and pmtk October 9, 2025 16:47
@kasturinarra kasturinarra mentioned this pull request Oct 9, 2025
Closed
@kasturinarra
Copy link
Contributor Author

kasturinarra commented Oct 10, 2025

@agullon could you please help review ? thanks !!

@ggiguash
Copy link
Contributor

ggiguash commented Oct 10, 2025

/lgtm
/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 10, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 10, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 10, 2025

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/lgtm
/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 10, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, kasturinarra

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 Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 10, 2025
@jerpeter1
Copy link
Member

jerpeter1 commented Oct 10, 2025

/label staff-eng-approved

@openshift-ci openshift-ci bot added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 10, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 10, 2025

/retest-required

Remaining retests: 0 against base HEAD 2f9cedd and 2 for PR HEAD c98e767 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 10, 2025

@kasturinarra: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit e06d7e4 into openshift:release-4.20 Oct 10, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@agullon agullon Awaiting requested review from agullon

@pmtk pmtk Awaiting requested review from pmtk

Assignees

@ggiguash ggiguash

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@kasturinarra @openshift-ci-robot @ggiguash @jerpeter1