Learn the concept behind serving engine namespaces


Namespaces in a ML Serving project are organization entities for your models. It allows user to simply classify their models depending on their needs by attaching them to an existing namespace.

Each namespace is linked to an object storage container of the same public cloud project where users can upload their serialized machine learning models. That object storage container is configurable.

Each namespace is also linked to a docker registry. The default docker registry is an OVHcloud provided one but this can be configured.


  • Number of created namespaces is restricted to 100 maximum per public cloud user.
  • Each namespace is linked to one and only object storage container of the same public cloud project.
  • Each namespace is linked to one and only docker registry.
  • Each namespace can contain as many models as the user wants.
  • Each model deployed inside a namespace will be reachable from the same base url such as https://<id-of-namespace>.<cx> where <id-of-namespace> will be a generated unique identifier of the namespace and <cx> the identifier of your assigned cluster.

Under the hood

Namespaces in a ML Serving project correspond to namespaces in a kubernetes cluster.

Going further

Did you find this guide useful?

Please feel free to give any suggestions in order to improve this documentation.

Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.

Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.

Thank you. Your feedback has been received.

These guides might also interest you...

OVHcloud Community

Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.

Discuss with the OVHcloud community

In accordance with the 2006/112/CE Directive, modified on 01/01/2015, prices exclude VAT. VAT may vary according to the customer's country of residence.