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.

Sign up for GitHub

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

Jump to bottom

[Story]: Migration of existing clusters to kserve #1975

Closed
lucferbux opened this issue Oct 17, 2023 · 0 comments · Fixed by #1957
Closed

[Story]: Migration of existing clusters to kserve #1975

lucferbux opened this issue Oct 17, 2023 · 0 comments · Fixed by #1957
Assignees
@lucferbux
Labels
feature/model-serving Model Serving Feature kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. priority/high Important issue that needs to be resolved asap. Releases should not have too many of these.

Comments

@lucferbux
Copy link
Contributor

Goal

Add migration logic to

Dependency issue

Itemized goals

Main goal is to have this state in migration:

  • KServe will be disabled
  • ModelMesh will be enabled

To do that:

  1. Check if there's already a dashboardConfig in the cluster
  2. Check that both kserve and modelmesh are disabled
  3. Merge a new state in which modelmesh is enabled and kserve is disabled

Aspects continued elsewhere

No response

Mocks

No mocks
@lucferbux lucferbux added priority/high Important issue that needs to be resolved asap. Releases should not have too many of these. kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. feature/model-serving Model Serving Feature labels Oct 17, 2023
This was referenced Oct 17, 2023
Closed
Merged
Closed
@lucferbux lucferbux linked a pull request Oct 18, 2023 that will close this issue
Create dashboard configuration to control kserve and modelmesh #1957
Merged
7 tasks
@lucferbux lucferbux mentioned this issue Oct 18, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lucferbux lucferbux

Labels
feature/model-serving Model Serving Feature kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. priority/high Important issue that needs to be resolved asap. Releases should not have too many of these.
Projects
Internal tracking
Status: Done
ODH Dashboard Planning
Archived in project
ODH Feature Tracking
Status: No status
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Create dashboard configuration to control kserve and modelmesh lucferbux/odh-dashboard
1 participant
@lucferbux