Skip to content

Commit b3a79da

Browse files
scralyscraly
committed
feat: add other languages
1 parent d73a6e9 commit b3a79da

File tree

13 files changed

+1465
-1
lines changed

13 files changed

+1465
-1
lines changed

‎pages/platform/private-registry/eol-harbor-1.10/guide.de-de.md

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
---
2+
title: 'End Of Life (EOL) Harbor 1.10 - How to replicate and migrate your data to an Harbor 2.x'
3+
excerpt: 'Find out how to replicate an old private registry (in Harbor 1.1x) to a recent OVhcloud Managed Private Registry (in Harbor 2.x)'
4+
slug: eol-harbor-1.10
5+
section: 'Getting started'
6+
order: 06
7+
routes:
8+
canonical: 'https://docs.ovh.com/gb/en/private-registry/eol-harbor-1.10/'
9+
updated: 2023-03-09
10+
---
11+
12+
**Last updated 09th March, 2023.**
13+
14+
<style>
15+
pre {
16+
font-size: 14px;
17+
}
18+
pre.console {
19+
background-color: #300A24;
20+
color: #ccc;
21+
font-family: monospace;
22+
padding: 5px;
23+
margin-bottom: 5px;
24+
}
25+
pre.console code {
26+
border: solid 0px transparent;
27+
color: #ccc;
28+
font-family: monospace !important;
29+
font-size: 0.75em;
30+
}
31+
.small {
32+
font-size: 0.75em;
33+
}
34+
</style>
35+
36+
## Objective
37+
38+
OVHcloud Managed Private Registry service provides you a managed, authenticated Docker registry where you can privately store your Docker images.
39+
40+
Managed Private Registry is built on Open Source solutions, such as Docker, and the CNCF Harbor project, to guarantee its interoperability.
41+
42+
The Managed Private Registries based on Harbor 1.x will terminate on August, 1st 2023. So the aim of this guide is to show you how to create a new private registry (based on Harbor 2.x) and migrate your data from your 1.x private registry to this new one.
43+
44+
## Instructions
45+
46+
First, follow the [Creating a private registry](../creating-a-private-registry/) guide to create a new private registry named `my-new-registry` for example, with the latest version of Harbor.
47+
48+
![My new private registry](images/my-new-registry-02.png)
49+
50+
Follow the [Connecting to the UI](../connecting-to-the-ui/) guide to connect to your new private registry.
51+
52+
Now you will configure a replication between your old private registry (in Harbor 1.x) and the new one.
53+
54+
In the `Administration` menu, click on `Registries`{.action}.
55+
56+
![Create a replication between two registries](images/registries.png){.thumbnail}
57+
58+
Click on `New endpoint`{.action} button to create a replication endpoint.
59+
60+
Now fill the form with the following information:
61+
62+
- Provider: `Harbor`
63+
- Name: `harbor-1.10`
64+
- Endpoint URL: `<your Harbor 1.10 URL (https://xxxxxxxx.grax.container-registry.ovh.net/)>`
65+
- Access ID: `<Harbor 1.10 username>`
66+
- Access secret: `<Harbor 1.10 password>`
67+
68+
![New private registry endpoint](images/new-registry-endpoint.png){.thumbnail}
69+
70+
Click on `Test connection`{.action} button to ping the private registry and test your information.
71+
72+
![New private registry endpoint](images/connection-tested-ok.png){.thumbnail}
73+
74+
Click on `OK` button to save your information.
75+
76+
![New private registry endpoint](images/new-registry-endpoint-created.png){.thumbnail}
77+
78+
In the `Administration` menu, click on `Replications`{.action}.
79+
80+
![Replications](images/replications.png){.thumbnail}
81+
82+
Click on `New replication rule`{.action} button to create a new rule.
83+
84+
Now fill the form with the following information:
85+
86+
- Name: `harbor-1.10`
87+
- Replication mode: `Pull based`
88+
- Source registry: Select your registry started with `harbor-1.10-*`
89+
- Trigger mode: `Manual` or `Scheduled`
90+
91+
> [!primary]
92+
>
93+
> **Manual**: Replicate the resources manually when needed. Note: Deletion operations are not replicated.
94+
>
95+
> **Scheduled**: Replicate the resources periodically by defining a cron job. Note: Deletion operations are not replicated.
96+
97+
![New replicaton rule](images/new-replication-rule.png){.thumbnail}
98+
99+
Click on `Save`{.action} button to save your information.
100+
101+
![Replication rule created](images/replication-rule-created.png){.thumbnail}
102+
103+
To run manually a replication rule, select your replication rule and click on `Replicate` button.
104+
105+
![Replication rule](images/replicate-button.png){.thumbnail}
106+
107+
Then, click on `Replicate`{.action} button to run the replication.
108+
109+
![Replication rule](images/are-you-sure.png){.thumbnail}
110+
111+
You should see, in the `Executions` section, the status of the replication.
112+
113+
First your replication should be in `InProgress` status and then, after waiting several seconds, the status should change to `Succeeded`.
114+
115+
![Replication rule](images/execution-status.png){.thumbnail}
116+
![Replication rule](images/execution-status-success.png){.thumbnail}
117+
118+
> [!primary]
119+
>
120+
> If you run several times the same replications and you have Helm charts, the replication can fail the second time, but it will work.
121+
122+
Finally, you must reconfigure your Harbor instance (users, robot accounts, garbage collection, retention rules...).
123+
Once your registry is replicated, change both the Harbor URL and credentials in your CI/CD and deployment platform if not already done.

‎pages/platform/private-registry/eol-harbor-1.10/guide.en-asia.md

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
title: 'End Of Life (EOL) Harbor 1.10 - How to replicate and migrate your data to an Harbor 2.x'
3+
excerpt: 'Find out how to replicate an old private registry (in Harbor 1.1x) to a recent OVhcloud Managed Private Registry (in Harbor 2.x)'
4+
slug: eol-harbor-1.10
5+
section: 'Getting started'
6+
order: 06
7+
updated: 2023-03-09
8+
---
9+
10+
**Last updated 09th March, 2023.**
11+
12+
<style>
13+
pre {
14+
font-size: 14px;
15+
}
16+
pre.console {
17+
background-color: #300A24;
18+
color: #ccc;
19+
font-family: monospace;
20+
padding: 5px;
21+
margin-bottom: 5px;
22+
}
23+
pre.console code {
24+
border: solid 0px transparent;
25+
color: #ccc;
26+
font-family: monospace !important;
27+
font-size: 0.75em;
28+
}
29+
.small {
30+
font-size: 0.75em;
31+
}
32+
</style>
33+
34+
## Objective
35+
36+
OVHcloud Managed Private Registry service provides you a managed, authenticated Docker registry where you can privately store your Docker images.
37+
38+
Managed Private Registry is built on Open Source solutions, such as Docker, and the CNCF Harbor project, to guarantee its interoperability.
39+
40+
The Managed Private Registries based on Harbor 1.x will terminate on August, 1st 2023. So the aim of this guide is to show you how to create a new private registry (based on Harbor 2.x) and migrate your data from your 1.x private registry to this new one.
41+
42+
## Instructions
43+
44+
First, follow the [Creating a private registry](../creating-a-private-registry/) guide to create a new private registry named `my-new-registry` for example, with the latest version of Harbor.
45+
46+
![My new private registry](images/my-new-registry-02.png)
47+
48+
Follow the [Connecting to the UI](../connecting-to-the-ui/) guide to connect to your new private registry.
49+
50+
Now you will configure a replication between your old private registry (in Harbor 1.x) and the new one.
51+
52+
In the `Administration` menu, click on `Registries`{.action}.
53+
54+
![Create a replication between two registries](images/registries.png){.thumbnail}
55+
56+
Click on `New endpoint`{.action} button to create a replication endpoint.
57+
58+
Now fill the form with the following information:
59+
60+
- Provider: `Harbor`
61+
- Name: `harbor-1.10`
62+
- Endpoint URL: `<your Harbor 1.10 URL (https://xxxxxxxx.grax.container-registry.ovh.net/)>`
63+
- Access ID: `<Harbor 1.10 username>`
64+
- Access secret: `<Harbor 1.10 password>`
65+
66+
![New private registry endpoint](images/new-registry-endpoint.png){.thumbnail}
67+
68+
Click on `Test connection`{.action} button to ping the private registry and test your information.
69+
70+
![New private registry endpoint](images/connection-tested-ok.png){.thumbnail}
71+
72+
Click on `OK` button to save your information.
73+
74+
![New private registry endpoint](images/new-registry-endpoint-created.png){.thumbnail}
75+
76+
In the `Administration` menu, click on `Replications`{.action}.
77+
78+
![Replications](images/replications.png){.thumbnail}
79+
80+
Click on `New replication rule`{.action} button to create a new rule.
81+
82+
Now fill the form with the following information:
83+
84+
- Name: `harbor-1.10`
85+
- Replication mode: `Pull based`
86+
- Source registry: Select your registry started with `harbor-1.10-*`
87+
- Trigger mode: `Manual` or `Scheduled`
88+
89+
> [!primary]
90+
>
91+
> **Manual**: Replicate the resources manually when needed. Note: Deletion operations are not replicated.
92+
>
93+
> **Scheduled**: Replicate the resources periodically by defining a cron job. Note: Deletion operations are not replicated.
94+
95+
![New replicaton rule](images/new-replication-rule.png){.thumbnail}
96+
97+
Click on `Save`{.action} button to save your information.
98+
99+
![Replication rule created](images/replication-rule-created.png){.thumbnail}
100+
101+
To run manually a replication rule, select your replication rule and click on `Replicate` button.
102+
103+
![Replication rule](images/replicate-button.png){.thumbnail}
104+
105+
Then, click on `Replicate`{.action} button to run the replication.
106+
107+
![Replication rule](images/are-you-sure.png){.thumbnail}
108+
109+
You should see, in the `Executions` section, the status of the replication.
110+
111+
First your replication should be in `InProgress` status and then, after waiting several seconds, the status should change to `Succeeded`.
112+
113+
![Replication rule](images/execution-status.png){.thumbnail}
114+
![Replication rule](images/execution-status-success.png){.thumbnail}
115+
116+
> [!primary]
117+
>
118+
> If you run several times the same replications and you have Helm charts, the replication can fail the second time, but it will work.
119+
120+
Finally, you must reconfigure your Harbor instance (users, robot accounts, garbage collection, retention rules...).
121+
Once your registry is replicated, change both the Harbor URL and credentials in your CI/CD and deployment platform if not already done.

‎pages/platform/private-registry/eol-harbor-1.10/guide.en-au.md

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
title: 'End Of Life (EOL) Harbor 1.10 - How to replicate and migrate your data to an Harbor 2.x'
3+
excerpt: 'Find out how to replicate an old private registry (in Harbor 1.1x) to a recent OVhcloud Managed Private Registry (in Harbor 2.x)'
4+
slug: eol-harbor-1.10
5+
section: 'Getting started'
6+
order: 06
7+
updated: 2023-03-09
8+
---
9+
10+
**Last updated 09th March, 2023.**
11+
12+
<style>
13+
pre {
14+
font-size: 14px;
15+
}
16+
pre.console {
17+
background-color: #300A24;
18+
color: #ccc;
19+
font-family: monospace;
20+
padding: 5px;
21+
margin-bottom: 5px;
22+
}
23+
pre.console code {
24+
border: solid 0px transparent;
25+
color: #ccc;
26+
font-family: monospace !important;
27+
font-size: 0.75em;
28+
}
29+
.small {
30+
font-size: 0.75em;
31+
}
32+
</style>
33+
34+
## Objective
35+
36+
OVHcloud Managed Private Registry service provides you a managed, authenticated Docker registry where you can privately store your Docker images.
37+
38+
Managed Private Registry is built on Open Source solutions, such as Docker, and the CNCF Harbor project, to guarantee its interoperability.
39+
40+
The Managed Private Registries based on Harbor 1.x will terminate on August, 1st 2023. So the aim of this guide is to show you how to create a new private registry (based on Harbor 2.x) and migrate your data from your 1.x private registry to this new one.
41+
42+
## Instructions
43+
44+
First, follow the [Creating a private registry](../creating-a-private-registry/) guide to create a new private registry named `my-new-registry` for example, with the latest version of Harbor.
45+
46+
![My new private registry](images/my-new-registry-02.png)
47+
48+
Follow the [Connecting to the UI](../connecting-to-the-ui/) guide to connect to your new private registry.
49+
50+
Now you will configure a replication between your old private registry (in Harbor 1.x) and the new one.
51+
52+
In the `Administration` menu, click on `Registries`{.action}.
53+
54+
![Create a replication between two registries](images/registries.png){.thumbnail}
55+
56+
Click on `New endpoint`{.action} button to create a replication endpoint.
57+
58+
Now fill the form with the following information:
59+
60+
- Provider: `Harbor`
61+
- Name: `harbor-1.10`
62+
- Endpoint URL: `<your Harbor 1.10 URL (https://xxxxxxxx.grax.container-registry.ovh.net/)>`
63+
- Access ID: `<Harbor 1.10 username>`
64+
- Access secret: `<Harbor 1.10 password>`
65+
66+
![New private registry endpoint](images/new-registry-endpoint.png){.thumbnail}
67+
68+
Click on `Test connection`{.action} button to ping the private registry and test your information.
69+
70+
![New private registry endpoint](images/connection-tested-ok.png){.thumbnail}
71+
72+
Click on `OK` button to save your information.
73+
74+
![New private registry endpoint](images/new-registry-endpoint-created.png){.thumbnail}
75+
76+
In the `Administration` menu, click on `Replications`{.action}.
77+
78+
![Replications](images/replications.png){.thumbnail}
79+
80+
Click on `New replication rule`{.action} button to create a new rule.
81+
82+
Now fill the form with the following information:
83+
84+
- Name: `harbor-1.10`
85+
- Replication mode: `Pull based`
86+
- Source registry: Select your registry started with `harbor-1.10-*`
87+
- Trigger mode: `Manual` or `Scheduled`
88+
89+
> [!primary]
90+
>
91+
> **Manual**: Replicate the resources manually when needed. Note: Deletion operations are not replicated.
92+
>
93+
> **Scheduled**: Replicate the resources periodically by defining a cron job. Note: Deletion operations are not replicated.
94+
95+
![New replicaton rule](images/new-replication-rule.png){.thumbnail}
96+
97+
Click on `Save`{.action} button to save your information.
98+
99+
![Replication rule created](images/replication-rule-created.png){.thumbnail}
100+
101+
To run manually a replication rule, select your replication rule and click on `Replicate` button.
102+
103+
![Replication rule](images/replicate-button.png){.thumbnail}
104+
105+
Then, click on `Replicate`{.action} button to run the replication.
106+
107+
![Replication rule](images/are-you-sure.png){.thumbnail}
108+
109+
You should see, in the `Executions` section, the status of the replication.
110+
111+
First your replication should be in `InProgress` status and then, after waiting several seconds, the status should change to `Succeeded`.
112+
113+
![Replication rule](images/execution-status.png){.thumbnail}
114+
![Replication rule](images/execution-status-success.png){.thumbnail}
115+
116+
> [!primary]
117+
>
118+
> If you run several times the same replications and you have Helm charts, the replication can fail the second time, but it will work.
119+
120+
Finally, you must reconfigure your Harbor instance (users, robot accounts, garbage collection, retention rules...).
121+
Once your registry is replicated, change both the Harbor URL and credentials in your CI/CD and deployment platform if not already done.

0 commit comments

Comments
 (0)