Changes for page Rancher 2

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

From version 15.2
edited by Diana Strebkova
on 2025/12/12 13:40
Change comment: There is no comment for this version
To version 12.5
edited by Diana Strebkova
on 2025/12/12 12:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -368,29 +368,6 @@
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 two ways to migrate your repositories:
372 -
373 -1. ##Direct Transition (Editing the Existing Repository)##
374 -1*. Change the target to “OCI Repository”.
375 -1*. Update the URL as required (the repository name cannot be changed).
376 -1*. After saving, installed apps will automatically start using the updated repository.
377 -1*. (% class="box" %)
378 -(((
379 -Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
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 -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 -)))
383 -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:
384 -1*. Create a new OCI repository for each chart,
385 -1*. Keep the old ChartMuseum repo enabled during the migration,
386 -1*. Migrate applications gradually following the steps described here.
387 -
388 -This avoids disruptions and allows controlled migration.
389 -
390 -Special Case: Old Repo Targeting Multiple Chart Repos
391 -
392 -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.
393 -
394 394  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
395 395  
396 396  (% class="box" %)