Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 16.2
edited by Diana Strebkova
on 2025/12/12 14:03
Change comment: There is no comment for this version
To version 12.9
edited by Diana Strebkova
on 2025/12/12 13:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -368,33 +368,17 @@
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 -)))
371 +There are 2 ways to "migrate" the repos:
375 375  
376 -There are two ways to migrate your repositories:
373 +1. You can do the fast transition - edit already existing repository – choose //Target: OCI repository //and 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"
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).
381 -1*. After saving, installed apps will automatically start using the updated repository.
382 -1*. (% class="box" %)
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" %)
383 383  (((
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.
379 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
387 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 -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.**
395 395  
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 -
398 398  | Term | Meaning
399 399  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
400 400  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -417,12 +417,11 @@
417 417  11. Go to **Apps → Repositories**.
418 418  11. Disable the old HTTP(S)-based repository.
419 419  11. Keep it disabled until the migration is done.
420 -[[image:1765548124989-482.59.06.png||height="152" width="485"]]
421 421  1. ##Update Existing Applications to Use the New OCI Repo##
422 422  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
423 423  11. Go to **Apps → Installed Apps**.
424 424  11. Open the application that was deployed using the old repo.
425 -11. Click **Edit/Upgrade**.
408 +11. Click **Upgrade**.
426 426  11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
427 427  11. Choose the chart version you want to deploy (same or newer).
428 428  11. Click **Upgrade**.
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
© 2018-2025 T-Systems International GmbH