Changes for page Rancher 2

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

From version 14.3
edited by Diana Strebkova
on 2025/12/12 13:37
Change comment: There is no comment for this version
To version 13.1
edited by Diana Strebkova
on 2025/12/12 13:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -370,19 +370,22 @@
370 370  
371 371  There are two ways to migrate your repositories:
372 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 -(((
373 +1. Direct Transition (Editing the Existing Repository)
374 + You can modify the existing repository directly:
375 +11.Change the target to “OCI Repository”.
376 +11.Update the URL as required (the repository name cannot be changed).
377 +
378 +After saving, installed apps will automatically start using the updated repository.
379 +
379 379  Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
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 -)))
383 -1. Add New Repositories One by One (Recommended), prese
384 -This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can:
385 385  
384 +1. Add New Repositories One by One (Recommended)
385 +
386 +This approach allows a smooth transition while the old ChartMuseum repository continues to function.
387 +You can:
388 +
386 386  * Create a new OCI repository for each chart,
387 387  * Keep the old ChartMuseum repo enabled during the migration,
388 388  * Migrate applications gradually following the steps described in the main migration guide.