CNTRLPLANE-371: Update to Kubernetes v1.33.2

[bertinatto]

No description provided.

[jstuever]

@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]

@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]

What is the ETA for this to be merged?

[openshift-ci-robot]

@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.

Details

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.

[dfarrell07]

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]

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]

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]

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

[kevinrizza]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, kevinrizza

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:

• OWNERS [bertinatto]

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

[bertinatto]

/retest

[openshift-ci]

@bertinatto: 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.