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 16.2
edited by Diana Strebkova
on 2025/12/12 14:03
on 2025/12/12 14:03
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 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. During migration, please adapt your helm push commands and url's for new oci-compatible repository.** 374 +))) 375 + 371 371 There are two ways to migrate your repositories: 372 372 373 373 1. ##Direct Transition (Editing the Existing Repository)## ... ... @@ -384,20 +384,12 @@ 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 -(% class="box" %) 397 -((( 398 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** 399 -))) 400 - 401 401 | Term | Meaning 402 402 | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository. 403 403 | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). ... ... @@ -420,11 +420,12 @@ 420 420 11. Go to **Apps → Repositories**. 421 421 11. Disable the old HTTP(S)-based repository. 422 422 11. Keep it disabled until the migration is done. 420 +[[image:1765548124989-482.59.06.png||height="152" width="485"]] 423 423 1. ##Update Existing Applications to Use the New OCI Repo## 424 424 Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition. 425 425 11. Go to **Apps → Installed Apps**. 426 426 11. Open the application that was deployed using the old repo. 427 -11. Click **Upgrade**. 425 +11. Click **Edit/Upgrade**. 428 428 11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 429 429 11. Choose the chart version you want to deploy (same or newer). 430 430 11. Click **Upgrade**.
- 1765548124989-482.59.06.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.dianastrebkovat-systemscom - Size
-
... ... @@ -1,0 +1,1 @@ 1 +64.4 KB - Content