Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.8
edited by Diana Strebkova
on 2025/12/12 13:05
Change comment: There is no comment for this version
To version 11.2
edited by Diana Strebkova
on 2025/12/12 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -335,6 +335,7 @@
335 335  (% class="wikigeneratedid" %)
336 336  Click Create.
337 337  
338 +
338 338  (% class="wrapped" %)
339 339  |=(((
340 340  Field
... ... @@ -363,72 +363,105 @@
363 363  
364 364  === Migrating chart repositories in rancher to new OCI Repository format ===
365 365  
366 -(% class="box warningmessage" %)
367 -(((
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 -)))
367 +(% class="wikigeneratedid" %)
370 370  
371 -There are 2 ways to "migrate" the repos:
369 +##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)**.##
372 372  
373 -1. You can do the fast transition - edit already existing repository to choose Target: OCI repository, then the apps will pick app the change automatically. The only problem is that he OCI repositpry a
371 +To ensure a smooth transition, we recomment should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
374 374  
375 -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
373 +We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.
376 376  
377 -(% class="box" %)
378 -(((
379 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
380 -)))
375 +-----
381 381  
382 -| Term | Meaning
383 -| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
384 -| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
377 +## Terminology##
385 385  
386 -##__**Why This Migration Is Required:**__##
379 +| Term | Meaning |
380 +| |-|
381 +| **Old Repository** | The existing HTTP/HTTPS ChartMuseum repository. |
382 +| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). |
387 387  
388 -* ##ChartMuseum is deprecated and will be removed.##
389 -* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
390 -* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
384 +-----
391 391  
392 -## Migration Steps:##
386 +## Why This Migration Is Required
387 +- ChartMuseum is deprecated and will be removed.
388 +- Applications deployed from old repos keep a reference to that repo inside their labels.
389 +- Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions**.##
393 393  
394 -1. ##Create the New OCI Repository in Rancher##
395 -11. Go to **Apps → Repositories**.
396 -11. Add a new repository of type **OCI**.
397 -11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
398 -11. Point it to the new OCI endpoint.
399 -1. ##Disable the Old ChartMuseum Repository Temporarily## 
400 -##This step ensures that Rancher resolves charts from the new OCI repo.##
401 -11. Go to **Apps → Repositories**.
402 -11. Disable the old HTTP(S)-based repository.
403 -11. Keep it disabled until the migration is done.
404 -1. ##Update Existing Applications to Use the New OCI Repo##
405 -Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
406 -11. Go to **Apps → Installed Apps**.
407 -11. Open the application that was deployed using the old repo.
408 -11. Click **Upgrade**.
409 -11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
410 -11. Choose the chart version you want to deploy (same or newer).
411 -11. Click **Upgrade**.
412 -1. ##Re-enable the Old Repository (Optional) ##
413 -If you still need the old repo for other apps, re-enable it after the migration steps above.
414 -**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
391 +-----
415 415  
416 -----
393 +## Migration Steps##
417 417  
395 +### 1. Create the New OCI Repository in Rancher##
396 +
397 +1. Go to **Apps → Repositories**.
398 +2. Add a new repository of type **OCI**.
399 +3. Name it exactly like your old repo name (e.g. `<chart-repo-name>`).
400 +4. Point it to the new OCI endpoint.
401 +
402 +-----
403 +
404 +### 2. Disable the Old ChartMuseum Repository Temporarily
405 +This step ensures that Rancher resolves charts from the new OCI repo.##
406 +
407 +1. Go to **Apps → Repositories**.
408 +2. Disable the old HTTP(S)-based repository.
409 +3. Keep it disabled until the migration is done.
410 +
411 +-----
412 +
413 +### 3. Update Existing Applications to Use the New OCI Repo
414 +Applications deployed with the old repository still contain the old repo name in their metadata.
415 +You must upgrade them once to transition.##
416 +
417 +1. Go to **Apps → Installed Apps**.
418 +2. Open the application that was deployed using the old repo.
419 +3. Click **Upgrade**.
420 +4. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
421 +5. Choose the chart version you want to deploy (same or newer).
422 +6. Click **Upgrade**.
423 +
424 +After this upgrade:
425 +- Your application is now linked to the **new OCI repository**.
426 +- Rancher will show upgrade notifications only for versions available in the new repo.
427 +
428 +-----
429 +
430 +### 4. Re-enable the Old Repository (Optional)
431 +If you still need the old repo for other apps, re-enable it after the migration steps above.##
432 +
433 +> 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.
434 +
435 +-----
436 +
418 418  ## Reverting the Migration (If Needed)
419 419  If you want to move an app back to the old repository:##
420 420  
421 421  1. Temporarily disable the new OCI repo.
422 -1. Enable the old ChartMuseum repo.
423 -1. Open the application → **Upgrade**.
424 -1. Select the chart from the old repo.
425 -1. Save.
441 +2. Enable the old ChartMuseum repo.
442 +3. Open the application → **Upgrade**.
443 +4. Select the chart from the old repo.
444 +5. Save.
426 426  
427 427  This will reconnect the app to the old repository.
428 428  
429 -=
430 -Automated deployments with Jenkins =
448 +-----
431 431  
450 +## Summary
451 +- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
452 +- After upgrade, apps no longer track versions from the old repository.
453 +- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.##
454 +
455 +-----
456 +
457 +If you want, I can also generate:
458 +- a shorter version (1-pager),
459 +- a diagram,
460 +- a Rancher UI screenshot guide,
461 +- or a version tailored for your team’s internal wiki.
462 +
463 +
464 += Automated deployments with Jenkins =
465 +
432 432  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
433 433  
434 434  == Prerequisites ==
© 2018-2025 T-Systems International GmbH