Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.3
edited by Diana Strebkova
on 2025/12/12 12:26
Change comment: There is no comment for this version
To version 18.1
edited by Diana Strebkova
on 2025/12/12 14:12
Change comment: Uploaded new attachment "1765548750604-334.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -368,13 +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 -To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
372 -
373 373  (% class="box" %)
374 374  (((
375 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
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.**
376 376  )))
377 377  
376 +There are two ways to migrate your repositories:
377 +
378 +1. ##Direct Transition (Editing the Existing Repository)##
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 +(((
384 +Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
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 +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.**
395 +
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 +
378 378  | Term | Meaning
379 379  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
380 380  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -392,15 +392,18 @@
392 392  11. Add a new repository of type **OCI**.
393 393  11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
394 394  11. Point it to the new OCI endpoint.
395 -1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.##
415 +1. ##Disable the Old ChartMuseum Repository Temporarily## 
416 +##This step ensures that Rancher resolves charts from the new OCI repo.##
396 396  11. Go to **Apps → Repositories**.
397 397  11. Disable the old HTTP(S)-based repository.
398 398  11. Keep it disabled until the migration is done.
420 +[[image:1765548124989-482.59.06.png||height="152" width="485"]]
399 399  1. ##Update Existing Applications to Use the New OCI Repo##
400 400  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
401 401  11. Go to **Apps → Installed Apps**.
402 402  11. Open the application that was deployed using the old repo.
403 -11. Click **Upgrade**.
425 +11. Click **Edit/Upgrade**.
426 +[[image:1765548598644-830.png||height="138" width="811"]]
404 404  11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
405 405  11. Choose the chart version you want to deploy (same or newer).
406 406  11. Click **Upgrade**.
... ... @@ -421,9 +421,9 @@
421 421  
422 422  This will reconnect the app to the old repository.
423 423  
447 +=
448 +Automated deployments with Jenkins =
424 424  
425 -Automated deployments with Jenkins
426 -
427 427  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
428 428  
429 429  == Prerequisites ==
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
1765548598644-830.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +153.4 KB
Content
1765548750604-334.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +103.0 KB
Content
© 2018-2025 T-Systems International GmbH