Skip to content

NO-JIRA: 4.20 kube 1.32 #319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 2, 2025

Conversation

dusk125
Copy link

@dusk125 dusk125 commented Jun 11, 2025

Brings oauth-proxy to the version of kube used in Openshift 4.20 (for now, the bump to kube 1.33 is in progress)

@openshift-ci openshift-ci bot requested review from ibihim and liouk June 11, 2025 14:43
@dusk125 dusk125 force-pushed the 4.20-kube-1.32 branch 3 times, most recently from b6587d1 to 54b686d Compare June 17, 2025 15:18
@dusk125 dusk125 changed the title NOJIRA: 4.20 kube 1.32 NO-JIRA: 4.20 kube 1.32 Jun 24, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 24, 2025
@openshift-ci-robot
Copy link

@dusk125: This pull request explicitly references no jira issue.

In response to this:

Brings oauth-proxy to the version of kube used in Openshift 4.20 (for now, the bump to kube 1.33 is in progress)

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.

@ibihim
Copy link

ibihim commented Jul 2, 2025

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 2, 2025
@ibihim
Copy link

ibihim commented Jul 2, 2025

/lgtm

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

openshift-ci bot commented Jul 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, ibihim

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

openshift-ci bot commented Jul 2, 2025

@dusk125: The following test 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/okd-scos-e2e-aws-ovn 33cc2e0 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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 0c93b4e into openshift:master Jul 2, 2025
7 of 8 checks passed
@dusk125 dusk125 deleted the 4.20-kube-1.32 branch July 2, 2025 19:08
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: golang-github-openshift-oauth-proxy
This PR has been included in build golang-github-openshift-oauth-proxy-container-v4.20.0-202507022153.p0.g0c93b4e.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants