Skip to content

chore (deps) : update controller-runtime to v0.24.1#1642

Draft
rohanKanojia wants to merge 2 commits into
devfile:mainfrom
rohankanojia-forks:pr/bump-controller-runtime-0-24-1
Draft

chore (deps) : update controller-runtime to v0.24.1#1642
rohanKanojia wants to merge 2 commits into
devfile:mainfrom
rohankanojia-forks:pr/bump-controller-runtime-0-24-1

Conversation

@rohanKanojia

Copy link
Copy Markdown
Member

What does this PR do?

  • Bump sigs.k8s.io/controller-runtime from v0.23.3 to v0.24.1
  • Upgrade aligned Kubernetes dependencies from v0.35.0 to v0.36.0 (k8s.io/api, k8s.io/apimachinery, k8s.io/client-go, etc.)
  • Regenerate CRD and deployment manifests to reflect updated upstream OpenAPI schema descriptions (cosmetic only; no API field changes)

No application code changes were required — the operator compiles cleanly against the new dependencies.

Signed-off-by: Rohan Kumar rohaan@redhat.com

What issues does this PR fix or reference?

N/A — routine dependency maintenance. No linked issue.

Keeps DWO aligned with the supported controller-runtime / client-go version matrix (controller-runtime v0.24.x requires k8s.io/* v0.36). No functional bug fix or feature change.

Is it tested? How?

Tested locally, at the build and unit-test level. I also ran pre-release testing script to test basic deworkspace operator flow.

PR Checklist

  • E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)
    • v8-devworkspace-operator-e2e: DevWorkspace e2e test
    • v8-che-happy-path: Happy path for verification integration with Che

Signed-off-by: Rohan Kumar <rohaan@redhat.com>
…de to v0.24.1

Signed-off-by: Rohan Kumar <rohaan@redhat.com>
@openshift-ci

openshift-ci Bot commented Jun 9, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci

openshift-ci Bot commented Jun 9, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rohanKanojia
Once this PR has been reviewed and has the lgtm label, please assign dkwon17 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d1aafbac-a717-4722-b54b-0be64ed8f252

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@tolusha

tolusha commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Hi! I'm che-ai-assistant — I help with your pull requests.

Available commands:

  • /che-ai-assistant generate-che-doc — Generate a documentation PR based on this PR's changes
  • /che-ai-assistant ok-pr-review — Run a comprehensive PR review (summary, code review, deep review, impact analysis)
  • /che-ai-assistant help — Show this help message

@rohanKanojia

Copy link
Copy Markdown
Member Author

/ok-to-test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants