Skip to content

CNTRLPLANE-371: Update to Kubernetes v1.33.1 #1952

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

bertinatto
Copy link
Member

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 27, 2025
@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial March 27, 2025 16:44
Copy link
Contributor

openshift-ci bot commented Mar 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 27, 2025
@bertinatto bertinatto force-pushed the bump-v1.33 branch 2 times, most recently from ac5dffe to bfd1779 Compare April 1, 2025 17:07
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 4, 2025
@bertinatto bertinatto force-pushed the bump-v1.33 branch 2 times, most recently from 7a052d5 to ba2fbd3 Compare April 24, 2025 16:12
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 24, 2025
@jstuever
Copy link

jstuever commented May 7, 2025

@bertinatto Do you have a timeline for when you expect to merge this? Cloud-credential-operator's k8s upgrade blocked due to dependency on this repo.

@bertinatto
Copy link
Member Author

@bertinatto Do you have a timeline for when you expect to merge this? Cloud-credential-operator's k8s upgrade blocked due to dependency on this repo.

@jstuever this is a requirement step for the k8s 1.33 bump in openshift/kubernetes, which we're targeting for the second sprint of the release (if everything goes smoothly, which is often not the case). You can follow the work on #tmp-k8s-1-33 Slack channel.

@tpantelis
Copy link

What is the ETA for this to be merged?

@bertinatto bertinatto changed the title WIP: Bump v1.33 CNTRLPLANE-371: Update to Kubernetes v1.33.1 Jun 11, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 11, 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 11, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 11, 2025

@bertinatto: This pull request references CNTRLPLANE-371 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 epic to target the "4.20.0" version, but no target version was set.

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

vthapar added a commit to vthapar/submariner-addon that referenced this pull request Jun 13, 2025
Depends on openshift/library-go#1952

Signed-off-by: Vishal Thapar <5137689+vthapar@users.noreply.github.com>
@dfarrell07
Copy link

We (and I suspect many other projects) are blocked from bumping to 1.33 by this. Any chance we can go ahead and merge it? Thanks!

@bertinatto
Copy link
Member Author

We (and I suspect many other projects) are blocked from bumping to 1.33 by this. Any chance we can go ahead and merge it? Thanks!

This is part of a larger effort to bump openshift/kubernetes, which is far from trivial. Semi-daily updates of this effort are provided in #tmp-k8s-1-33 Slack channel.

@dfarrell07
Copy link

We (and I suspect many other projects) are blocked from bumping to 1.33 by this. Any chance we can go ahead and merge it? Thanks!

This is part of a larger effort to bump openshift/kubernetes, which is far from trivial. Semi-daily updates of this effort are provided in #tmp-k8s-1-33 Slack channel.

Great, following there thanks!

@dfarrell07
Copy link

For anyone else following along but not familiar with this workflow, the parent of the Jira mentioned in the title has something closer to a timeline estimate: https://issues.redhat.com/browse/OCPSTRAT-2019

Copy link
Contributor

openshift-ci bot commented Jun 20, 2025

@bertinatto: all tests passed!

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.

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants