Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 14.1
edited by Diana Strebkova
on 2025/12/12 13:32
Change comment: There is no comment for this version
To version 16.2
edited by Diana Strebkova
on 2025/12/12 14:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -368,43 +368,33 @@
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)##
374 -11. Change the target to “OCI Repository”.
375 -11. Update the URL as required (the repository name cannot be changed).
376 -
377 -1. Direct Transition (Editing the Existing Repository).You can modify the existing repository directly:
378 -Change the target to “OCI Repository”.Update the URL as required (the repository name cannot be changed).
379 -
380 -After saving, installed apps will automatically start using the updated repository.
381 -
379 +1*. Change the target to “OCI Repository”.
380 +1*. Update the URL as required (the repository name cannot be changed).
381 +1*. After saving, installed apps will automatically start using the updated repository.
382 +1*. (% class="box" %)
383 +(((
382 382  Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
383 383  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”).
384 384  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 +)))
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.**
385 385  
386 -1. Add New Repositories One by One (Recommended)
387 -
388 -This approach allows a smooth transition while the old ChartMuseum repository continues to function.
389 -You can:
390 -
391 -* Create a new OCI repository for each chart,
392 -* Keep the old ChartMuseum repo enabled during the migration,
393 -* Migrate applications gradually following the steps described in the main migration guide.
394 -
395 -This avoids disruptions and allows controlled migration.
396 -
397 -Special Case: Old Repo Targeting Multiple Chart Repos
398 -
399 -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.
400 -
401 401  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
402 402  
403 -(% class="box" %)
404 -(((
405 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
406 -)))
407 -
408 408  | Term | Meaning
409 409  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
410 410  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -427,11 +427,12 @@
427 427  11. Go to **Apps → Repositories**.
428 428  11. Disable the old HTTP(S)-based repository.
429 429  11. Keep it disabled until the migration is done.
420 +[[image:1765548124989-482.59.06.png||height="152" width="485"]]
430 430  1. ##Update Existing Applications to Use the New OCI Repo##
431 431  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
432 432  11. Go to **Apps → Installed Apps**.
433 433  11. Open the application that was deployed using the old repo.
434 -11. Click **Upgrade**.
425 +11. Click **Edit/Upgrade**.
435 435  11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
436 436  11. Choose the chart version you want to deploy (same or newer).
437 437  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
© 2018-2025 T-Systems International GmbH