Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 22.1
edited by Diana Strebkova
on 2025/12/12 14:23
Change comment: There is no comment for this version
To version 12.15
edited by Diana Strebkova
on 2025/12/12 13:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -249,9 +249,9 @@
249 249  
250 250  oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
251 251  
252 -{{box}}
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 is not supported in rancher.
254 -{{/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}}
255 255  )))
256 256  
257 257  {{info}}
... ... @@ -287,8 +287,8 @@
287 287  (% class="p1" %)
288 288  Create a new Repository by pressing the Create button.
289 289  
290 -(% class="p1" id="HTarget:http28s29URL-1" %)
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"]]
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"]] ====
292 292  
293 293  (% id="HTarget:http28s29URL-1" class="p1" %)
294 294  ==== Target: http(s) URL ====
... ... @@ -361,7 +361,7 @@
361 361  {{/info}}
362 362  )))
363 363  
364 -== Migrating chart repositories in rancher to new OCI Repository format ==
364 +=== Migrating chart repositories in rancher to new OCI Repository format ===
365 365  
366 366  (% class="box warningmessage" %)
367 367  (((
... ... @@ -368,34 +368,42 @@
368 368  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)**.
369 369  )))
370 370  
371 -(% class="box" %)
372 -(((
373 -**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.**
374 -)))
375 -
376 376  There are two ways to migrate your repositories:
377 377  
378 -1. ##Direct Transition (Editing the Existing Repository)##
379 -1*. Change the target to “OCI Repository”.
380 -1*. Update the URL as required (the repository name cannot be changed), check **Target: OCI Repository** documentation above
381 -1*. After saving, installed apps will automatically start using the updated repository.
382 -1*. (% class="box" %)
383 -(((
373 +1. Direct Transition (Editing the Existing Repository)
374 + You can modify the existing repository directly:
375 +Change the target to “OCI Repository”.
376 +
377 +* Update the URL as required (the repository name cannot be changed).
378 +
379 +After saving, installed apps will automatically start using the updated repository.
380 +
384 384  Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
385 385  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”).
386 386  The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
387 -)))
388 -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:
389 -1*. Create a new OCI repository for each chart,
390 -1*. Keep the old ChartMuseum repo enabled during the migration,
391 -1*. Migrate applications gradually following the steps described here.
392 -1*. This avoids disruptions and allows controlled migration.
393 -
394 -1. //Special Case: Old Repo Targeting Multiple Chart Repos//
395 -If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
396 396  
385 +1. Add New Repositories One by One (Recommended)
386 +
387 +This approach allows a smooth transition while the old ChartMuseum repository continues to function.
388 +You can:
389 +
390 +* Create a new OCI repository for each chart,
391 +* Keep the old ChartMuseum repo enabled during the migration,
392 +* Migrate applications gradually following the steps described in the main migration guide.
393 +
394 +This avoids disruptions and allows controlled migration.
395 +
396 +Special Case: Old Repo Targeting Multiple Chart Repos
397 +
398 +If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please contact support. OCI does not support multi-chart endpoints within a single repository, and we can help you find an appropriate solution.
399 +
397 397  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
398 398  
402 +(% class="box" %)
403 +(((
404 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
405 +)))
406 +
399 399  | Term | Meaning
400 400  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
401 401  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -411,7 +411,7 @@
411 411  1. ##Create the New OCI Repository in Rancher##
412 412  11. Go to **Apps → Repositories**.
413 413  11. Add a new repository of type **OCI**.
414 -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.**__
422 +11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
415 415  11. Point it to the new OCI endpoint.
416 416  1. ##Disable the Old ChartMuseum Repository Temporarily## 
417 417  ##This step ensures that Rancher resolves charts from the new OCI repo.##
... ... @@ -418,15 +418,12 @@
418 418  11. Go to **Apps → Repositories**.
419 419  11. Disable the old HTTP(S)-based repository.
420 420  11. Keep it disabled until the migration is done.
421 -[[image:1765548124989-482.59.06.png||height="152" width="485"]]
422 422  1. ##Update Existing Applications to Use the New OCI Repo##
423 423  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
424 424  11. Go to **Apps → Installed Apps**.
425 425  11. Open the application that was deployed using the old repo.
426 -11. Click **Edit/Upgrade**.
427 -[[image:1765548598644-830.png||height="138" width="811"]]
428 -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:
429 -[[image:1765548750604-334.png||height="293" width="308"]]
433 +11. Click **Upgrade**.
434 +11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
430 430  11. Choose the chart version you want to deploy (same or newer).
431 431  11. Click **Upgrade**.
432 432  1. ##Re-enable the Old Repository (Optional) ##
... ... @@ -433,7 +433,9 @@
433 433  If you still need the old repo for other apps, re-enable it after the migration steps above.
434 434  **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
435 435  
436 -##
441 +----
442 +
443 +## Reverting the Migration (If Needed)
437 437  If you want to move an app back to the old repository:##
438 438  
439 439  1. Temporarily disable the new OCI repo.
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-2025 T-Systems International GmbH