Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.4
edited by Diana Strebkova
on 2025/12/12 12:27
Change comment: There is no comment for this version
To version 19.1
edited by Diana Strebkova
on 2025/12/12 14:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -288,7 +288,7 @@
288 288  Create a new Repository by pressing the Create button.
289 289  
290 290  (% id="HTarget:http28s29URL-1" class="p1" %)
291 -==== [[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]] ====
291 +[[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]]
292 292  
293 293  (% id="HTarget:http28s29URL-1" class="p1" %)
294 294  ==== Target: http(s) URL ====
... ... @@ -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`).
... ... @@ -390,7 +390,7 @@
390 390  1. ##Create the New OCI Repository in Rancher##
391 391  11. Go to **Apps → Repositories**.
392 392  11. Add a new repository of type **OCI**.
393 -11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
413 +11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). __**You can't name it the same and can't rename it later.**__
394 394  11. Point it to the new OCI endpoint.
395 395  1. ##Disable the Old ChartMuseum Repository Temporarily## 
396 396  ##This step ensures that Rancher resolves charts from the new OCI repo.##
... ... @@ -397,12 +397,15 @@
397 397  11. Go to **Apps → Repositories**.
398 398  11. Disable the old HTTP(S)-based repository.
399 399  11. Keep it disabled until the migration is done.
420 +[[image:1765548124989-482.59.06.png||height="152" width="485"]]
400 400  1. ##Update Existing Applications to Use the New OCI Repo##
401 401  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
402 402  11. Go to **Apps → Installed Apps**.
403 403  11. Open the application that was deployed using the old repo.
404 -11. Click **Upgrade**.
405 -11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
425 +11. Click **Edit/Upgrade**.
426 +[[image:1765548598644-830.png||height="138" width="811"]]
427 +11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. Or enter the chart name in search bar:
428 +[[image:1765548750604-334.png||height="293" width="308"]]
406 406  11. Choose the chart version you want to deploy (same or newer).
407 407  11. Click **Upgrade**.
408 408  1. ##Re-enable the Old Repository (Optional) ##
... ... @@ -409,9 +409,7 @@
409 409  If you still need the old repo for other apps, re-enable it after the migration steps above.
410 410  **Note:** Even if a newer chart version exists in the old repository, your migrated app **will not see it**, because it is no longer connected to that repo
411 411  
412 -----
413 -
414 -## Reverting the Migration (If Needed)
435 +##
415 415  If you want to move an app back to the old repository:##
416 416  
417 417  1. Temporarily disable the new OCI repo.
... ... @@ -422,9 +422,9 @@
422 422  
423 423  This will reconnect the app to the old repository.
424 424  
446 +=
447 +Automated deployments with Jenkins =
425 425  
426 -Automated deployments with Jenkins
427 -
428 428  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
429 429  
430 430  == 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