Skip to Content

Changes for page Rancher 2

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

Summary

Details

Page properties
Content
... ... @@ -368,14 +368,8 @@
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 -There are 2 ways to "migrate" the repos:
371 +To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
372 372  
373 -1. You can do direct transition and edit already existing repository – choose //Target: OCI repository, //adapt the url as shown above (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The issue is that the OCI repository needs to target chart repos in the url, not the whole folder anymore.  That means if you previously deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket", other repos updates wont be working anymore and you will still need to create a new repo targeting each chartrepo.
374 -1. Or you can add new repositories one by one taking your time, while the old chartmuseum repo will still be functioning suring migraiton. For this, you can see the next described migration process.
375 -1. If you
376 -
377 -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
378 -
379 379  (% class="box" %)
380 380  (((
381 381  **We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
... ... @@ -398,13 +398,12 @@
398 398  11. Add a new repository of type **OCI**.
399 399  11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
400 400  11. Point it to the new OCI endpoint.
401 -1. ##Disable the Old ChartMuseum Repository Temporarily## 
402 -##This step ensures that Rancher resolves charts from the new OCI repo.##
395 +1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.##
403 403  11. Go to **Apps → Repositories**.
404 404  11. Disable the old HTTP(S)-based repository.
405 405  11. Keep it disabled until the migration is done.
406 406  1. ##Update Existing Applications to Use the New OCI Repo##
407 -Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
400 +##Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.##
408 408  11. Go to **Apps → Installed Apps**.
409 409  11. Open the application that was deployed using the old repo.
410 410  11. Click **Upgrade**.
... ... @@ -411,26 +411,41 @@
411 411  11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
412 412  11. Choose the chart version you want to deploy (same or newer).
413 413  11. Click **Upgrade**.
414 -1. ##Re-enable the Old Repository (Optional) ##
415 -If you still need the old repo for other apps, re-enable it after the migration steps above.
416 -**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
407 +1. ##Re-enable the Old Repository (Optional) If you still need the old repo for other apps, re-enable it after the migration steps above.##
417 417  
418 -----
409 + 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.
419 419  
411 +-----
412 +
420 420  ## Reverting the Migration (If Needed)
421 421  If you want to move an app back to the old repository:##
422 422  
423 423  1. Temporarily disable the new OCI repo.
424 -1. Enable the old ChartMuseum repo.
425 -1. Open the application → **Upgrade**.
426 -1. Select the chart from the old repo.
427 -1. Save.
417 +2. Enable the old ChartMuseum repo.
418 +3. Open the application → **Upgrade**.
419 +4. Select the chart from the old repo.
420 +5. Save.
428 428  
429 429  This will reconnect the app to the old repository.
430 430  
431 -=
432 -Automated deployments with Jenkins =
424 +-----
433 433  
426 +## Summary
427 +- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
428 +- After upgrade, apps no longer track versions from the old repository.
429 +- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.##
430 +
431 +-----
432 +
433 +If you want, I can also generate:
434 +- a shorter version (1-pager),
435 +- a diagram,
436 +- a Rancher UI screenshot guide,
437 +- or a version tailored for your team’s internal wiki.
438 +
439 +
440 += Automated deployments with Jenkins =
441 +
434 434  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
435 435  
436 436  == Prerequisites ==
© 2018-2025 T-Systems International GmbH