Bump to v2.235.0

[lsm5]

It's been over 3 months since the last release and there's been at least a couple of changes that users would be looking for.

@haircommander @rhatdan @wrabcak PTAL

Summary by Sourcery

Chores:

• Bump the version to v2.235.0.

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5

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:

• OWNERS [lsm5]

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

[sourcery-ai]

Hey @lsm5 - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[haircommander]

/lgtm

[openshift-ci]

@haircommander: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

[lsm5]

@haircommander: changing LGTM is restricted to collaborators

Weird why that happened. Looking into this.

[lsm5]

Looks like OWNERS needs a reviewer section. Adding it in another PR.

[lsm5]

$ git log core-services/prow/02_config/containers/container-selinux/OWNERS
commit 605470c7fe025a491f3b019c830f9e9987cb79cc
Author: OpenShift Bot <openshift-bot@redhat.com>
Date:   Thu Feb 20 13:35:38 2025

    Sync OWNERS files by autoowners job at Thu, 20 Feb 2025 07:41:41 UTC (#61870)

The OWNERS file in mergebot only got updated about 3 hours ago. So, I guess a slash-lgtm should work with a retry. The OWNERS file shouldn't need any changes.

[haircommander]

/lgtm

👀

[openshift-ci]

@haircommander: changing LGTM is restricted to collaborators

In response to this:

/lgtm

👀

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.

[haircommander]

I wonder if i'm in the org...

[lsm5]

I wonder if i'm in the org...

I do see Member listed against your name. I'll check with the mergebot folks.

[lsm5]

@haircommander I added you to the Collaborator list just now. Try again please.

[haircommander]

/lgtm

[lsm5]

/cherrypick rhaos-maint

[lsm5]

/cherrypick rhaos-maint

[openshift-cherrypick-robot]

@lsm5: new pull request created: #362

In response to this:

/cherrypick rhaos-maint

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.