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
on 2025/12/12 13:00
Change comment:
There is no comment for this version
To version 14.1
edited by Diana Strebkova
on 2025/12/12 13:32
on 2025/12/12 13:32
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,10 +368,36 @@ 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 2ways to"migrate"therepos:371 +There are two ways to migrate your repositories: 372 372 373 -1. 373 +1. ##Direct Transition (Editing the Existing Repository)## 374 +11. Change the target to “OCI Repository”. 375 +11. Update the URL as required (the repository name cannot be changed). 374 374 377 +1. Direct Transition (Editing the Existing Repository).You can modify the existing repository directly: 378 +Change the target to “OCI Repository”.Update the URL as required (the repository name cannot be changed). 379 + 380 +After saving, installed apps will automatically start using the updated repository. 381 + 382 +Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder. 383 +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”). 384 +The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart. 385 + 386 +1. Add New Repositories One by One (Recommended) 387 + 388 +This approach allows a smooth transition while the old ChartMuseum repository continues to function. 389 +You can: 390 + 391 +* Create a new OCI repository for each chart, 392 +* Keep the old ChartMuseum repo enabled during the migration, 393 +* Migrate applications gradually following the steps described in the main migration guide. 394 + 395 +This avoids disruptions and allows controlled migration. 396 + 397 +Special Case: Old Repo Targeting Multiple Chart Repos 398 + 399 +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. 400 + 375 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 376 377 377 (% class="box" %)