Skip to content
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

Merged

Conversation

zdtsw
Copy link
Member

@zdtsw zdtsw commented Oct 1, 2024

Description

  • 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
  • some not related changes in BiasMetrics function

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

  • keep a ODC CR with disableModelRegistry: true
  • keep a DSCI with release 2.13.0 from previous installation
  • install local build
  • check ODC CR see disableModelRegistry: true

For downstream case

  • keep a ODC CR with disableModelRegistry: true
  • keep a DSCI with release 2.13.0 from previous installation
  • fake cluster to be a Managed one
  • install local build
  • check ODC CR see disableModelRegistry: false

Screenshot or short clip

Merge criteria

  • You have read the contributors guide.
  • Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
  • Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

@openshift-ci openshift-ci bot requested review from ajaypratap003 and lphiri October 1, 2024 09:06
@zdtsw zdtsw requested review from ykaliuta, andrewballantyne and VaishnaviHire and removed request for lphiri and ajaypratap003 October 1, 2024 09:06
}
return nil
}
ctrl.Log.Info("Upgrade does not force BiasMetrics to false due to from release >= 2.14.0")
Copy link
Contributor

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]>
Copy link

openshift-ci bot commented Oct 1, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Oct 1, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 1a441e7 into opendatahub-io:incubation Oct 1, 2024
8 checks passed
zdtsw referenced this pull request in zdtsw-forking/rhods-operator Oct 1, 2024
…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)
openshift-merge-bot bot referenced this pull request in red-hat-data-services/rhods-operator Oct 1, 2024
…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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants