Skip to Content

Changes for page Rancher 2

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

Summary

Details

Page properties
Content
... ... @@ -368,6 +368,11 @@
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 +
371 371  There are two ways to migrate your repositories:
372 372  
373 373  1. ##Direct Transition (Editing the Existing Repository)##
... ... @@ -380,25 +380,16 @@
380 380  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”).
381 381  The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
382 382  )))
383 -1. Add New Repositories One by One (Recommended), preserve the old one till the end.
384 -This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can:
385 -1.* Create a new OCI repository for each chart,
386 -1.* Keep the old ChartMuseum repo enabled during the migration,
387 -1.* Migrate applications gradually following the steps described here.
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 +1. //Special Case: Old Repo Targeting Multiple Chart Repos//
394 +If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
388 388  
389 -This avoids disruptions and allows controlled migration.
390 -
391 -Special Case: Old Repo Targeting Multiple Chart Repos
392 -
393 -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.
394 -
395 395  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
396 396  
397 -(% class="box" %)
398 -(((
399 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
400 -)))
401 -
402 402  | Term | Meaning
403 403  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
404 404  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -421,12 +421,15 @@
421 421  11. Go to **Apps → Repositories**.
422 422  11. Disable the old HTTP(S)-based repository.
423 423  11. Keep it disabled until the migration is done.
420 +[[image:1765548124989-482.59.06.png||height="152" width="485"]]
424 424  1. ##Update Existing Applications to Use the New OCI Repo##
425 425  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
426 426  11. Go to **Apps → Installed Apps**.
427 427  11. Open the application that was deployed using the old repo.
428 -11. Click **Upgrade**.
429 -11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
425 +11. Click **Edit/Upgrade**.
426 +[[image:1765548598644-830.png||height="138" width="811"]]
427 +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:
428 +[[image:1765548750604-334.png||height="293" width="308"]]
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,9 +433,7 @@
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 -----
437 -
438 -## Reverting the Migration (If Needed)
435 +##Reverting the Migration (If Needed)
439 439  If you want to move an app back to the old repository:##
440 440  
441 441  1. Temporarily disable the new OCI repo.
1765548124989-482.59.06.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +64.4 KB
Content
1765548598644-830.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +153.4 KB
Content
1765548750604-334.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +103.0 KB
Content
© 2018-2025 T-Systems International GmbH