Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 15.3
edited by Diana Strebkova
on 2025/12/12 13:55
on 2025/12/12 13:55
Change comment:
There is no comment for this version
To version 14.3
edited by Diana Strebkova
on 2025/12/12 13:37
on 2025/12/12 13:37
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -380,14 +380,19 @@ 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 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 -1*. This avoids disruptions and allows controlled migration. 388 -1. //Special Case: Old Repo Targeting Multiple Chart Repos// 389 -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. 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: 390 390 386 +* Create a new OCI repository for each chart, 387 +* Keep the old ChartMuseum repo enabled during the migration, 388 +* Migrate applications gradually following the steps described in the main migration guide. 389 + 390 +This avoids disruptions and allows controlled migration. 391 + 392 +Special Case: Old Repo Targeting Multiple Chart Repos 393 + 394 +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. 395 + 391 391 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 392 392 393 393 (% class="box" %)