Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 15.2
edited by Diana Strebkova
on 2025/12/12 13:40
on 2025/12/12 13:40
Change comment:
There is no comment for this version
To version 15.1
edited by Diana Strebkova
on 2025/12/12 13:38
on 2025/12/12 13:38
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -380,10 +380,11 @@ 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. 383 +1. Add New Repositories One by One (Recommended), preserve the old one till the end. 384 +This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can: 385 +1.* Create a new OCI repository for each chart, 386 +1.* Keep the old ChartMuseum repo enabled during the migration, 387 +1.* Migrate applications gradually following the steps described here. 387 387 388 388 This avoids disruptions and allows controlled migration. 389 389