-
Notifications
You must be signed in to change notification settings - Fork 151
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
feat: add support for upgrade to force disableModelRegistry to false #1269
feat: add support for upgrade to force disableModelRegistry to false #1269
Conversation
pkg/upgrade/upgrade.go
Outdated
} | ||
return nil | ||
} | ||
ctrl.Log.Info("Upgrade does not force BiasMetrics to false due to from release >= 2.14.0") |
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.
seems a copy/paste
- seems duplicate to create a new function but mainly: - can have a different value for the version - if we want to keep one and remove another just comment out function - probably we will have some other with similar logic later till it can be done in UI logic Signed-off-by: Wen Zhou <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ykaliuta 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 |
1a441e7
into
opendatahub-io:incubation
…ed-hat-data-services#1269) - seems duplicate to create a new function but mainly: - can have a different value for the version - if we want to keep one and remove another just comment out function - probably we will have some other with similar logic later till it can be done in UI logic Signed-off-by: Wen Zhou <[email protected]> (cherry picked from commit 1a441e7)
…1269) - seems duplicate to create a new function but mainly: - can have a different value for the version - if we want to keep one and remove another just comment out function - probably we will have some other with similar logic later till it can be done in UI logic Signed-off-by: Wen Zhou <[email protected]> (cherry picked from commit 1a441e7)
Description
https://issues.redhat.com/browse/RHOAIENG-13604
How Has This Been Tested?
local build: quay.io/wenzhou/opendatahub-operator-catalog:v2.14.13604
For ODH case
disableModelRegistry: true
disableModelRegistry: true
For downstream case
disableModelRegistry: true
disableModelRegistry: false
Screenshot or short clip
Merge criteria