Skip to content

Commit 50af9c3

Browse files
H4516022YH4516022Y
authored
Update guide.en-gb.md
1 parent fc1119a commit 50af9c3

File tree

1 file changed

+38
-44
lines changed
  • pages/public_cloud/containers_orchestration/reversbility/oci_registry

1 file changed

+38
-44
lines changed

‎pages/public_cloud/containers_orchestration/reversbility/oci_registry/guide.en-gb.md

Lines changed: 38 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,76 +1,70 @@
1-
# Reversibility Policy for the “OCI” Product
1+
,---
2+
title: Managed OCI artifact Registry Product Reversibility Policy
3+
updated: 2025-06-10
4+
---
25

36
## Objective
47

5-
This document outlines the reversibility policy for the product line (OCI).
8+
This document describes the reversibility policy of the Managed OCI artifact Registry product corresponding to the OVHcloud solution: Managed Private Registry
69

7-
This policy aims to implement general reversibility principles and our compliance with the SWIPO IaaS Code of Conduct for cloud providers.
10+
This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers.
811

12+
## Feature List
913

14+
The product features are divided into three categories:
1015

11-
## List of Features
16+
- **Main features** for which we guarantee migration capacity.
17+
- **OVHcloud implementations** that require adaptation to a new migration environment.
18+
- **Specific features** that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.
1219

13-
The features of the “Product” are divided into three categories:
1420

15-
- **Core features** for which we guarantee migration capability.
16-
- **OVHcloud implementations** that require adaptation to a new environment for migration.
17-
- **Specific features** that cannot be guaranteed for migration as they are tied to the OVHcloud environment or involve custom developments.
1821

22+
## Main features
1923

24+
| Feature| Description | Formats | Migration model | Documentation available |
25+
| --- | --- | --- | --- | --- |
26+
| **OCI API and OCI compatibility** | Native OCI (Open Container Initiative) support for artifacts, images, Helm charts, Cosign signatures, and more. | OCI, Helm, Cosign (signatures), JSON | **Inbound** : Direct push of artifacts via standard tools (docker, helm, oras, cosign, etc.) or OCI API.<br>**Outbound** : Pull/export of artifacts via the same tools or API to any other OCI/Harbor/Artifact Registry compatible registry. | [Migrate Helm Chart from Chartmuseum to OCI](/pages/public_cloud/containers_orchestration/managed_private_registry/migrate-helm-charts-from-chartmuseum-to-oci)|
27+
| **Import/Export Artifacts** | Upload and download artifacts (push/pull) via CLI/API standard Harbor/OCI | OCI, Helm, JSON | **Inbound**:Import via docker push, helm push, oras push, etc.<br>**Outbound** : Export via docker pull, helm pull, oras pull, then push to the target. | [Artifact Import/Export](/pages/public_cloud/containers_orchestration/managed_private_registry/migrate-helm-charts-from-chartmuseum-to-oci) |
28+
| **Signature and verification Cosign** | Signature and verification of artifacts via Cosign (Sigstore), Harbor v2.5+ native support | Cosign (OCI signature) | **Inbound** : Import of Cosign signed artifacts.<br>**Outbound** : Export of Cosign artifacts and their signatures, reimport possible on any Cosign/OCI compatible registry. | [ Sign OCI artifacts with Cosign on OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/sign-artifacts-with-cosign) |
29+
| **Replication Harbor** | Automatic synchronization/replication between Harbor/OCI registries (push/pull or bidirectional) | OCI, Helm, JSON | **Inbound**: Configuring replication from a source registry (Harbor/OCI) to OVHcloud.<br>**Outbound**: Configuring replication to another Harbor/OCI-compatible registry. | [Replication Configuration](goharbour.io/docs/2.0.0/administration/configuration-replication/)|
2030

21-
## Core Features
2231

23-
| Feature | Description | Formats | Migration Model | Documentation Available |
24-
|--------------------------|----------------------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
25-
| **OCI API and Compatibility** | Native support for the OCI (Open Container Initiative) format for artifacts, images, Helm charts, Cosign signatures, etc. | OCI, Helm, Cosign (signatures), JSON | **Inbound**: Direct artifact push via standard tools (docker, helm, oras, cosign, etc.) or via OCI API.<br>**Outbound**: Pull/export using the same tools or API to any OCI/Harbor/Artifact Registry-compatible registry. | [OCI API and Compatibility](https://help.ovhcloud.com/csm/fr-public-cloud-private-registry-migrate-helm-charts?id=kb_article_view&sysparm_article=KB0058870)|
26-
| **Artifact Import/Export** | Upload and download of artifacts (push/pull) via standard Harbor/OCI CLI/API | OCI, Helm, JSON | **Inbound**: Import via `docker push`, `helm push`, `oras push`, etc.<br>**Outbound**: Export via `docker pull`, `helm pull`, `oras pull`, then push to the target. | [Artifact Import/Export](https://help.ovhcloud.com/csm/fr-public-cloud-private-registry-migrate-helm-charts?id=kb_article_view&sysparm_article=KB0058870)|
27-
| **Cosign Signature** | Signature and verification via Cosign (Sigstore), support native in Harbor >= v2.5 | Cosign (OCI signature) | **Inbound**: Import of artifacts signed with Cosign.<br>**Outbound**: Export of artifacts with signatures, reusable on any Cosign/OCI registry compatible. | [ Sign OCI artifacts with Cosign on OVHcloud Managed Private Registry ](https://help.ovhcloud.com/csm/fr-public-cloud-private-registry-sign-artifacts-with-cosign?id=kb_article_view&sysparm_article=KB0059137)|
28-
| **Replication Harbor** | Synchronisation automatique entre registres Harbor/OCI (push/pull ou bidirectionnelle) | OCI, Helm, JSON | **Inbound**: Configuration of replication from a source registry (Harbor/OCI).<br>**Outbound**: Replication to another compatible Harbor/OCI registry. | [Configuring Replication](goharbor.io/docs/2.0.0/administration/configuring-replication/)|
29-
## OVHcloud Implementation
32+
## OVHcloud implementation
3033

31-
| Feature | Description | Available Formats | Migration Model | Documentation Available |
32-
|------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
33-
| **RBAC and management of rights** | Management of access rights by project, user, robot account, RBAC Harbor | JSON (policies), interne Harbor | **Entrante** : Adaptation manuelle of rights during import.<br>**Sortante** : Export of artefacts, then reconfiguration of rights on the target. |[Managing users and projects](https://help.ovhcloud.com/csm/fr-public-cloud-private-registry-managing-users-projects?id=kb_article_view&sysparm_article=KB0055968)|
34-
| **Audit logs** | Automatic logging of access and operations (logs Harbor/OVHcloud) | JSON, logs internes | **Entrante** : Non applicable to import.<br>**Sortante** : Manual export of logs if needed, adaptation necessary according to the target.|[Access and Search Project Logs](https://goharbor.io/docs/2.3.0/working-with-projects/project-configuration/access-project-logs/)|
35-
| **CI/CD Automation** | Integration with CI/CD pipelines via Harbor/OCI API, robot tokens, OIDC | JSON, YAML (pipelines) | **Entrante** : Adaptation of pipelines to point to OVHcloud.<br>**Sortante** : Reconfiguration of pipelines to the new target, potential adaptation of tokens. | [Harbor API](https://api.harbor.gg/docs/index.html)|
36-
| **Vulnerability scanning** | Automatic image analysis via integrated Harbor scanner (Trivy, Clair, etc.) | JSON, CSV reports | **Entrante** : Non applicable to import.<br>**Sortante** : Export of reports possible, adaptation to be foreseen for the target according to the scan tool used.|[Clair project](https://clairproject.org/)|
34+
| Feature| Description | Formats | Migration model | Documentation available |
35+
| --- | --- | --- | --- | --- |
36+
| **RBAC and rights management** | Manage access rights by project, user, robot account, RBAC Harbor | JSON (policies), interne Harbor | **Incoming**: Permissions are adjusted manually during import.<br>**Outgoing**: Artifacts are exported, then permissions are reconfigured on the target (RBAC format not always compatible between solutions). |[Managing users and projects](/pages/public_cloud/containers_orchestration/managed_private_registry/managing-users-and-projects)|
37+
| **Audit logs and logs** | Automatic access logging and operations (Harbor/OVHcloud logs) | JSON, internal logs | **Incoming**: Not applicable for import.<br>**Outgoing**: Manually export logs if required, adaptation required depending on the target (format/non-standardized logs).|[Access and Search Project Logs](https://goharbour.io/docs/2.3.0/working-with-projects/project-configuration/access-project-logs/) |
38+
| **CI/CD Automation** | Integration with CI/CD pipelines via Harbor/OCI API, robot tokens, OIDC | JSON, YAML (pipelines) | **Incoming**: Adapting scripts/pipelines to point to the OVHcloud registry.<br>**Outgoing**: Reconfiguring pipelines to point to the new target, potential tokens adaptation and permissions.| [Harbor API](https://api.harbor.gg/docs/index.html)|
39+
| **Vulnerability Scans** | Automatic image analysis via an integrated Harbor scanner (Trivy, Clair, etc.) | JSON CSV Reports | **Inbound**: Not applicable for import.<br>**Outbound**: Reports can be exported, but the target may need to be adapted if it has another scanner.|[Clair project](https://clairproject.org/)|
3740

3841

39-
## Specific Features
42+
## Specific features
4043

41-
| Function | Description | Formats Available | Migration Model | Documentation Available |
42-
|------------------------|---------------------------------------------------------------------------------------|--------------------|----------------------------------------------------------------------------------------------------|--------------------------|
43-
| **OVHcloud Manager/API** | OVHcloud-specific graphical interface and API for managing clusters and resources | N/A | **Incoming**: N/A<br>**Outgoing**: Scripts and automation must be rewritten for the target provider; manual management may be required. | [OVHcloud API specification ](https://eu.api.ovh.com/console/?section=%2FallDom&branch=v1)|
44-
| **Infrastructure as Code** | Automated deployment via OVHcloud-specific Terraform modules | N/A | **Inbound migration:** Scripts need to be adapted for other providers. <br> **Outbound migration:** Configuration rewrite required for Terraform. | [Terraform](https://registry.terraform.io/providers/ovh/ovh/latest/docs) |
44+
| Feature| Description | Formats | Migration model | Documentation available |
45+
| --- | --- | --- | --- | --- |
46+
| **Managed via the OVHcloud Control Panel** | OVHcloud-specific graphical interface and API for service management | N/A | **Inbound**: N/A<br>**Outbound**: Scripts/API to rewrite for the target, manual management required. | [OVHcloud API ](https://eu.api.ovh.com/console/?section=%2FallDom&branch=v1)|
47+
| **Infrastructure as Code** | Automated deployment via Terraform modules specific to OVHcloud | N/A | **Inbound:** Scripts must be adapted for other providers. <br> **Outbound:** Terraform configurations need to be rewritten. | [Terraform](https://registry.terraform.io/providers/ovh/ovh/latest/docs) |
4548

4649

4750

48-
## List of Architectures
49-
50-
The OVHcloud Managed Private Registry service (based on Harbor) supports a multi-project, multi-namespace, and multi-user architecture with logical isolation. It enables automatic replication between registries (Harbor/OCI), fine-grained access control (RBAC), OIDC authentication, artifact signing and verification (Cosign), vulnerability scanning, and CI/CD integration via API or robot tokens.
51-
The service is highly available and can be integrated with the OVHcloud vRack private network for secure usage.
52-
51+
## List of architectures
5352

53+
The OVHcloud Managed Private Registry service (based on Harbor) supports a multi-project, multi-namespace, multi-user architecture with logical isolation. It enables automatic replication between registries (Harbor/OCI), fine-grained rights management (RBAC), OIDC authentication, artifact signing and verification (Cosign), vulnerability scanning, and CI/CD integration via API or robot tokens. The service is highly available and can be integrated into the OVHcloud vRack private network for secure usage.
5454

5555
## Partner Services
5656

57-
OVHcloud partners are listed under the keyword **"Cloud Migration"** in the dedicated partner directory.
58-
59-
OVHcloud also offers a dedicated service: [**OVHcloud Professional Services**](https://www.ovhcloud.com/fr/professional-services/).
57+
OVHcloud partners are listed under the keyword **“Migrate to the cloud”** in the Dedicated Partner Directory.
6058

59+
OVHcloud also offers a dedicated service: [**OVHcloud Professional Services**](https://www.ovhcloud.com/en-gb/professional-services/).
6160

6261

63-
## Cost and Fees
6462

65-
Billing is usage-based with no commitment.
66-
There are **no termination fees**: deleting the service immediately stops billing.
67-
Any associated **OVHcloud credits are non-transferable**.
63+
## Cost and fees
6864

69-
Clients are responsible for exporting their artifacts before deletion, as data removal is irreversible.
65+
You are billed on a pay-per-use basis, with no commitment. No specific cancelation fees apply: deleting the service will stop the billing immediately. Any associated OVHcloud credits cannot be transferred. It is the customer’s responsibility to export their artifacts before deletion, as deleting them is irreversible.
7066

7167

72-
## Data Retention After Contract Termination
68+
## Retention of data after termination of contract
7369

74-
After service deletion or contract termination, OVHcloud **permanently deletes all artifacts, images, signatures, and metadata** stored in the registry.
75-
Access logs and history are also removed.
76-
It is therefore **critical to export all necessary data prior to deletion**, as restoration is not possible afterward.
70+
After deletion of the service or termination of the contract, OVHcloud permanently deletes all artifacts, images, signatures and metadata stored in the registry. Logs and access histories are also deleted. It is therefore imperative to export all necessary data before deletion, as no restoration is possible after the cancelation.

0 commit comments

Comments
 (0)