-
Notifications
You must be signed in to change notification settings - Fork 86
chore: bump model registry dependency to 0.3.3 #596
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
Al-Pragliola
wants to merge
2
commits into
opendatahub-io:incubating
Choose a base branch
from
Al-Pragliola:al-pragliola-bump-mr-dep-20251111
base: incubating
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify controller-runtime v0.21.0 compatibility with Kubernetes v0.33.5.
The PR bumps controller-runtime to v0.21.0 in line with Kubernetes API/apimachinery/client-go updates to v0.33.5. Additionally, line 174 contains a replace directive for KEDA compatibility that pins controller-runtime to v0.19.1. Verify that:
🌐 Web query:
💡 Result:
Yes. controller-runtime v0.21.0 targets the k8s.io/* 0.33 line (bumped to v0.33.0), so using Kubernetes/client-go/apimachinery v0.33.5 is compatible (patch releases within the same minor are supported). [1][2]
Sources:
[1] controller-runtime compatibility table (README).
[2] controller-runtime v0.21.0 release notes.
Length of output: 384
🏁 Script executed:
Length of output: 79967
🏁 Script executed:
Length of output: 63
🌐 Web query:
💡 Result:
Short answer: controller-runtime v0.21 is a breaking-minor bump (k8s.io/* → v0.33, Go 1.24, several API/behavior changes) so it is not drop‑in compatible with older controller-runtime minors; KEDA has reported incompatibility problems with controller-runtime ≥ v0.20 (webhook.Validator/deprecated webhook API issues). See the controller-runtime release notes/versioning and the KEDA issue for details. [1][2][3]
Sources
Conflicting controller-runtime versions in go.mod: line 34 declares v0.21.0 but line 174 replace directive forces v0.19.1.
The replace directive at line 174 overrides the v0.21.0 specified at line 34, meaning the actual controller-runtime version will be v0.19.1, not v0.21.0. While KEDA has reported incompatibility with controller-runtime ≥ v0.20 (validating the workaround), this creates a contradiction in the PR:
Clarify the intent and reconcile these conflicting directives.
🤖 Prompt for AI Agents