Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 15.5
edited by Diana Strebkova
on 2025/12/12 13:59
on 2025/12/12 13:59
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
-
... ... @@ -368,11 +368,6 @@ 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. During migration, please adapt your helm push commands and url's for new oci-compatible repository.** 374 -))) 375 - 376 376 There are two ways to migrate your repositories: 377 377 378 378 1. ##Direct Transition (Editing the Existing Repository)## ... ... @@ -385,16 +385,25 @@ 385 385 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”). 386 386 The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart. 387 387 ))) 388 -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: 389 -1*. Create a new OCI repository for each chart, 390 -1*. Keep the old ChartMuseum repo enabled during the migration, 391 -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.** 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. 395 395 389 +This avoids disruptions and allows controlled migration. 390 + 391 +Special Case: Old Repo Targeting Multiple Chart Repos 392 + 393 +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. 394 + 396 396 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 397 397 397 +(% class="box" %) 398 +((( 399 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** 400 +))) 401 + 398 398 | Term | Meaning 399 399 | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository. 400 400 | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). ... ... @@ -417,7 +417,6 @@ 417 417 11. Go to **Apps → Repositories**. 418 418 11. Disable the old HTTP(S)-based repository. 419 419 11. Keep it disabled until the migration is done. 420 - 421 421 1. ##Update Existing Applications to Use the New OCI Repo## 422 422 Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition. 423 423 11. Go to **Apps → Installed Apps**.