Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23

From version 12.6
edited by Diana Strebkova
on 2025/12/12 13:00
Change comment: There is no comment for this version
To version 17.1
edited by Diana Strebkova
on 2025/12/12 14:09
Change comment: Uploaded new attachment "1765548598644-830.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -368,17 +368,33 @@
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 -There are 2 ways to "migrate" the repos:
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 +)))
372 372  
373 -1.
376 +There are two ways to migrate your repositories:
374 374  
375 -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
376 -
377 -(% class="box" %)
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).
381 +1*. After saving, installed apps will automatically start using the updated repository.
382 +1*. (% class="box" %)
378 378  (((
379 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
384 +Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
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 +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 380  )))
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.**
381 381  
396 +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
397 +
382 382  | Term | Meaning
383 383  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
384 384  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -401,11 +401,12 @@
401 401  11. Go to **Apps → Repositories**.
402 402  11. Disable the old HTTP(S)-based repository.
403 403  11. Keep it disabled until the migration is done.
420 +[[image:1765548124989-482.59.06.png||height="152" width="485"]]
404 404  1. ##Update Existing Applications to Use the New OCI Repo##
405 405  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
406 406  11. Go to **Apps → Installed Apps**.
407 407  11. Open the application that was deployed using the old repo.
408 -11. Click **Upgrade**.
425 +11. Click **Edit/Upgrade**.
409 409  11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
410 410  11. Choose the chart version you want to deploy (same or newer).
411 411  11. Click **Upgrade**.
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