Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.15
edited by Diana Strebkova
on 2025/12/12 13:22
on 2025/12/12 13:22
Change comment:
There is no comment for this version
To version 12.14
edited by Diana Strebkova
on 2025/12/12 13:20
on 2025/12/12 13:20
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,35 +368,12 @@ 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 twoways to migrateyourrepositories:371 +There are 2 ways to "migrate" the repos: 372 372 373 -1. DirectTransition (Editing theExistingRepository)374 - You canmodifythe existing repositorydirectly:375 - Changethe target to“OCIRepository”.373 +1. You can do direct transition and edit already existing repository – choose //Target: OCI repository, //adapt the url as shown above (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The issue is that the OCI repository needs to target chart repos in the url, not the whole folder anymore. That means if you previously deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket", other repos updates wont be working anymore and you will still need to create a new repo targeting each chartrepo. 374 +1. Or you can add new repositories one by one taking your time, while the old chartmuseum repo will still be functioning suring migraiton. For this, you can see the next described migration process. 375 +1. If you have a repo targeting multiple repos and need that the new OCI repo behaves as the previous one, please contact support for finding out the solution. 376 376 377 -* Update the URL as required (the repository name cannot be changed). 378 - 379 -After saving, installed apps will automatically start using the updated repository. 380 - 381 -Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder. 382 -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”). 383 -The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart. 384 - 385 -1. Add New Repositories One by One (Recommended) 386 - 387 -This approach allows a smooth transition while the old ChartMuseum repository continues to function. 388 -You can: 389 - 390 -* Create a new OCI repository for each chart, 391 -* Keep the old ChartMuseum repo enabled during the migration, 392 -* Migrate applications gradually following the steps described in the main migration guide. 393 - 394 -This avoids disruptions and allows controlled migration. 395 - 396 -Special Case: Old Repo Targeting Multiple Chart Repos 397 - 398 -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. 399 - 400 400 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 401 401 402 402 (% class="box" %)