search

kserve / modelmesh-serving

Controller for ModelMesh
Apache License 2.0
203 stars 114 forks source link

Change ModelMesh Serving controller to work with multiple namespaces #33

Closed chinhuang007 closed 8 months ago

chinhuang007 commented 3 years ago

The current ModelMesh Serving is namespace scoped, meaning all of its components must exist within a single namespace and only one instance of ModelMesh Serving can be installed per namespace. The idea is to make ModelMesh Serving cluster scoped so that one set of controller components can serve multiple namespaces.

The limitation of having a controller and a set of Serving Runtimes in each namespace means sharing is not possible between namespaces and would cause unnecessarily high resource consumption when ModelMesh Serving is installed in different namespaces.

At a high level, we would like to change Serving Runtimes to be cluster scoped and make the controller to manage resources across namespaces. Here is the doc with more details, including a couple of possible solutions. The doc will be updated whenever decisions are made and implementations are identified.

chinhuang007 commented 3 years ago

@yuzisun Please help review and suggest/identify a solution that would work naturally in the KServe community and Kube ecosystem. Thanks!

rafvasq commented 8 months ago

Closed by https://github.com/kserve/modelmesh-serving/pull/84.