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

[Feature Request]: Allow to use both model serving modes in the same project #2145

Closed
bdattoma opened this issue Nov 15, 2023 · 2 comments
Closed
Labels
feature/model-serving Model Serving Feature kind/enhancement New functionality request (existing augments or new additions) migrated needs-info Further information is requested from the reporter or from another source priority/normal An issue with the product; fix when possible

Comments

@bdattoma
Copy link

Feature description

We are moving towards having ModelMesh and KServe working together in the cluster, it has still some issues, but it can work already.

We should consider adding more flexibility in the DS Projects about using both the tools in the same DS Project.

Describe alternatives you've considered

if there are reasons not to have this option implemented, I think we should at least work on giving the option to change the selected serving mode - #2144

Anything else?

No response

@bdattoma bdattoma added kind/enhancement New functionality request (existing augments or new additions) priority/normal An issue with the product; fix when possible untriaged Indicates the newly create issue has not been triaged yet labels Nov 15, 2023
@lucferbux
Copy link
Contributor

Hi @bdattoma the model serving team (cc @Jooho @Xaenalt ) are working to support both ModelMesh and KServe in the same DS Project in the future, but we don't have the possibility right now to do so. We'll add that feature once it's supported by the controllers.

In the meantime, the alternative of change the selected serving mode could be feasible, we would need UX, but it's a matter of removing all the model serving resources and change lables in the project. That's something we can support in the meantime. cc @vconzola

@manaswinidas manaswinidas added needs-info Further information is requested from the reporter or from another source feature/model-serving Model Serving Feature and removed untriaged Indicates the newly create issue has not been triaged yet labels Nov 20, 2023
@dgutride
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/model-serving Model Serving Feature kind/enhancement New functionality request (existing augments or new additions) migrated needs-info Further information is requested from the reporter or from another source priority/normal An issue with the product; fix when possible
Projects
Archived in project
Development

No branches or pull requests

4 participants