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.4
edited by Diana Strebkova
on 2025/12/12 13:56
on 2025/12/12 13:56
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,6 +368,11 @@ 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 +(% class="box" %) 372 +((( 373 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. After m** 374 +))) 375 + 371 371 There are two ways to migrate your repositories: 372 372 373 373 1. ##Direct Transition (Editing the Existing Repository)## ... ... @@ -384,13 +384,10 @@ 384 384 1*. Create a new OCI repository for each chart, 385 385 1*. Keep the old ChartMuseum repo enabled during the migration, 386 386 1*. Migrate applications gradually following the steps described here. 392 +1*. This avoids disruptions and allows controlled migration. 393 +1. //Special Case: Old Repo Targeting Multiple Chart Repos// 394 +If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.** 387 387 388 -This avoids disruptions and allows controlled migration. 389 - 390 -Special Case: Old Repo Targeting Multiple Chart Repos 391 - 392 -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. 393 - 394 394 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 395 395 396 396 (% class="box" %)