Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2026/04/20 09:21
From version 24.2
edited by Diana Strebkova
on 2026/04/20 09:12
Change comment: There is no comment for this version
To version 12.11
edited by Diana Strebkova
on 2025/12/12 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -177,6 +177,49 @@
177 177  (% class="p1" %)
178 178  [[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]]
179 179  
180 +(% id="H" class="p1" %)
181 +==== Target: http(s) URL ====
182 +
183 +{{warning}}
184 +This example is being deprecated, you can still add other external repositories in that way, but all internal harbor-hosted repositories should be added as Target: OCI Repository
185 +{{/warning}}
186 +
187 +(% class="p1" %)
188 +In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
189 +
190 +(% class="wrapped" %)
191 +|=(((
192 +Field
193 +)))|=(((
194 +Value
195 +)))
196 +|=(((
197 +Name
198 +)))|(((
199 +devops-as-a-service
200 +)))
201 +|=(((
202 +Description
203 +)))|(((
204 +Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
205 +)))
206 +|=(((
207 +Index URL
208 +)))|(((
209 +[[https:~~/~~/registry.sdc.t-systems.net/chartrepo/devopsaas/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]]
210 +)))
211 +
212 +[[image:attach:image-2024-2-27_14-29-17.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="540"]]
213 +
214 +(% class="p1" %)
215 +Finally, click Create.
216 +
217 +The repository is now listed:
218 +
219 +[[image:Screenshot 2024-07-03 at 15.13.55.png||data-xwiki-image-style-border="true" height="149" width="785"]]
220 +
221 +==== Target: OCI Repository ====
222 +
180 180  To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
181 181  
182 182  [[image:1765207154466-828.png||height="298" width="821"]]
... ... @@ -204,11 +204,11 @@
204 204  )))|(((
205 205  oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
206 206  
207 -oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-auto-agent
250 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
208 208  
209 -{{box}}
210 -Take into account, that all internal harbor repositories with helm charts have PKEY-helm naming convention, adding repo with both docker images and helm charts is not supported in rancher.
211 -{{/box}}
252 +{{info}}
253 +Take into account, that all internal harbor repositories with helm charts have PKEY-helm naming convention, adding repo with both docker images and helm charts may not be supported in rancher.
254 +{{/info}}
212 212  )))
213 213  
214 214  {{info}}
... ... @@ -244,8 +244,8 @@
244 244  (% class="p1" %)
245 245  Create a new Repository by pressing the Create button.
246 246  
247 -(% class="p1" id="HTarget:http28s29URL-1" %)
248 -[[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]]
290 +(% id="HTarget:http28s29URL-1" class="p1" %)
291 +==== [[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]] ====
249 249  
250 250  (% id="HTarget:http28s29URL-1" class="p1" %)
251 251  ==== Target: http(s) URL ====
... ... @@ -318,7 +318,7 @@
318 318  {{/info}}
319 319  )))
320 320  
321 -== Migrating chart repositories in rancher to new OCI Repository format ==
364 +=== Migrating chart repositories in rancher to new OCI Repository format ===
322 322  
323 323  (% class="box warningmessage" %)
324 324  (((
... ... @@ -325,34 +325,18 @@
325 325  ChartMuseum is being deprecated. After the migration is complete, **all harbor charts will be removed from ChartMuseum**, and **old HTTP(S)-based chart repositories will no longer work in Rancher (for internal harbor charts)**.
326 326  )))
327 327  
328 -(% class="box" %)
329 -(((
330 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. During migration, please adapt your helm push commands and url's for new oci-compatible repository.**
331 -)))
371 +There are 2 ways to "migrate" the repos:
332 332  
333 -There are two ways to migrate your repositories:
373 +1. You can do direct transition  and edit already existing repository – choose //Target: OCI repository, //adapt the url (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The problem is that the OCI repository recommends to target chart repos in the url, not the whole folder anymore.  That means if you deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket", you will still need to create a new repo targeting "jira".
374 +1. Or you can add new repositories one by
334 334  
335 -1. ##Direct Transition (Editing the Existing Repository)##
336 -1*. Change the target to “OCI Repository”.
337 -1*. Update the URL as required (the repository name cannot be changed), check **Target: OCI Repository** documentation above
338 -1*. After saving, installed apps will automatically start using the updated repository.
339 -1*. (% class="box" %)
376 +To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. If you don't w
377 +
378 +(% class="box" %)
340 340  (((
341 -Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
342 -If your old repository included several charts (for example “bitbucket” and “jira”), then after switching to OCI you can only target one chart (e.g. “bitbucket”).
343 -The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
380 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
344 344  )))
345 -1. Add New Repositories One by One (Recommended), preserve the old one till the end. This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can:
346 -1*. Create a new OCI repository for each chart,
347 -1*. Keep the old ChartMuseum repo enabled during the migration,
348 -1*. Migrate applications gradually following the steps described here.
349 -1*. This avoids disruptions and allows controlled migration.
350 -
351 -1. //Special Case: Old Repo Targeting Multiple Chart Repos//
352 -If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
353 353  
354 -To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. If you don't w
355 -
356 356  | Term | Meaning
357 357  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
358 358  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -368,7 +368,7 @@
368 368  1. ##Create the New OCI Repository in Rancher##
369 369  11. Go to **Apps → Repositories**.
370 370  11. Add a new repository of type **OCI**.
371 -11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). __**You can't name it the same and can't rename it later.**__
398 +11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
372 372  11. Point it to the new OCI endpoint.
373 373  1. ##Disable the Old ChartMuseum Repository Temporarily## 
374 374  ##This step ensures that Rancher resolves charts from the new OCI repo.##
... ... @@ -375,15 +375,12 @@
375 375  11. Go to **Apps → Repositories**.
376 376  11. Disable the old HTTP(S)-based repository.
377 377  11. Keep it disabled until the migration is done.
378 -[[image:1765548124989-482.59.06.png||height="152" width="485"]]
379 379  1. ##Update Existing Applications to Use the New OCI Repo##
380 380  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
381 381  11. Go to **Apps → Installed Apps**.
382 382  11. Open the application that was deployed using the old repo.
383 -11. Click **Edit/Upgrade**.
384 -[[image:1765548598644-830.png||height="138" width="811"]]
385 -11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. Or enter the chart name in search bar:
386 -[[image:1765548750604-334.png||height="293" width="308"]]
409 +11. Click **Upgrade**.
410 +11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
387 387  11. Choose the chart version you want to deploy (same or newer).
388 388  11. Click **Upgrade**.
389 389  1. ##Re-enable the Old Repository (Optional) ##
... ... @@ -390,8 +390,11 @@
390 390  If you still need the old repo for other apps, re-enable it after the migration steps above.
391 391  **Note:** Even if a newer chart version exists in the old repository, your migrated app **will not see it**, because it is no longer connected to that repo
392 392  
393 -##If you want to move an app back to the old repository:##
417 +----
394 394  
419 +## Reverting the Migration (If Needed)
420 +If you want to move an app back to the old repository:##
421 +
395 395  1. Temporarily disable the new OCI repo.
396 396  1. Enable the old ChartMuseum repo.
397 397  1. Open the application → **Upgrade**.
... ... @@ -400,7 +400,8 @@
400 400  
401 401  This will reconnect the app to the old repository.
402 402  
403 -= Automated deployments with Jenkins =
430 +=
431 +Automated deployments with Jenkins =
404 404  
405 405  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
406 406  
1765548124989-482.59.06.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -64.4 KB
Content
1765548598644-830.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -153.4 KB
Content
1765548750604-334.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -103.0 KB
Content
© 2018-2026 T-Systems International GmbH