Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From 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
To version 12.12
edited by Diana Strebkova
on 2025/12/12 13:16
on 2025/12/12 13:16
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -370,9 +370,8 @@ 370 370 371 371 There are 2 ways to "migrate" the repos: 372 372 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. 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", you will still need to create a new repo targeting "jira". 374 +1. Or you can add new repositories one by 376 376 377 377 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 378 378