Here are the most frequently asked questions about Managed Private Registry (Harbor).
In which regions is the Private Registry solution available?
Private Registry is currently available in Vint Hill, Virginia (VIN) and Hillsboro, Oregon (HIL).
What are the Managed Private Registry service dependencies?
The MPR (Managed Private Registry) service is managed by our teams relying on compute resources and network from Public Cloud and on Object Storage S3 standard. Those dependencies are neither visible nor billed.
Find below the exact locations of the dependencies:
|Object Storage S3 standard
What version of Harbor is offered?
All new Private Registry services use Harbor 2.x. We regularly backport security and performance patches from the latest versions and will regularly propose new feature upgrades.
What service levels are included in the Private Registry service?
Private Registry is covered by a service level (SLA) that guarantees very high availability to assure you of the high efficiency of your developments and deployments. M and L plans have an SLA that also covers components such as the user interface and vulnerability scanning. You will find all the details in the Special Conditions for OVHcloud Public Cloud Service.
Do I have to use the OVHcloud Managed Kubernetes Service with Private Registry?
No, because by subscribing to the Private Registry service you will have your own Docker Registry and your own Harbor (API and GUI). Once you receive your IDs, you will be able to use the Private Registry service with any container or orchestrator tool, like the OVHcloud Kubernetes solution or another one.
As a Private Registry user, do I have the option to switch plans?
You can migrate to a plan with a larger capacity at any time. As soon as you notify us of your wish for evolution, the new limits are taken into account in tens of seconds without any data loss or configuration changes required.