Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 16.1
edited by Diana Strebkova
on 2025/12/12 14:02
on 2025/12/12 14:02
Change comment:
Uploaded new attachment "1765548124989-482.59.06.png", version {1}
To 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
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 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)## ... ... @@ -389,12 +389,20 @@ 389 389 1*. Create a new OCI repository for each chart, 390 390 1*. Keep the old ChartMuseum repo enabled during the migration, 391 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.** 395 395 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 + 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 396 +(% class="box" %) 397 +((( 398 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** 399 +))) 400 + 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**.
- 1765548124989-482.59.06.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.dianastrebkovat-systemscom - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.4 KB - Content