Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.9
edited by Diana Strebkova
on 2025/12/12 13:10
Change comment: There is no comment for this version
To version 11.1
edited by Diana Strebkova
on 2025/12/12 12:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -281,6 +281,7 @@
281 281  (% class="p1" %)
282 282  In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
283 283  
284 +(% class="p1" %)
284 284  
285 285  [[image:attach:Screenshot 2023-04-25 at 13.11.48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="400" width="209"]]
286 286  
... ... @@ -335,6 +335,7 @@
335 335  (% class="wikigeneratedid" %)
336 336  Click Create.
337 337  
339 +
338 338  (% class="wrapped" %)
339 339  |=(((
340 340  Field
... ... @@ -363,72 +363,103 @@
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 -)))
368 +# Migration Guide: ChartMuseum → OCI-based Chart Repositories in Rancher
370 370  
371 -There are 2 ways to "migrate" the repos:
370 +## Overview
371 +ChartMuseum is being deprecated. After the migration is complete, **all charts will be removed from ChartMuseum**, and **old HTTP(S)-based chart repositories will no longer work in Rancher**.
372 372  
373 -1. You can do the fast transition - edit already existing repository – choose //Target: OCI repository //and adapt the url (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The problem is that the OCI repository recommends to target chart repos in the url, not the whole folder anymore.  That means if you deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket"
373 +To ensure a smooth transition, each project 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
375 +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 -)))
377 +---
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`).
379 +## Terminology
380 +| Term | Meaning |
381 +|------|---------|
382 +| **Old Repository** | The existing HTTP/HTTPS ChartMuseum repository. |
383 +| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). |
385 385  
386 -##__**Why This Migration Is Required:**__##
385 +---
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**.##
387 +## Why This Migration Is Required
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**.
391 391  
392 -## Migration Steps:##
392 +---
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) ##
394 +## Migration Steps
395 +
396 +### 1. Create the New OCI Repository in Rancher
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)
413 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
415 415  
416 -----
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.
417 417  
418 -## Reverting the Migration (If Needed)
419 -If you want to move an app back to the old repository:##
435 +---
420 420  
437 +## Reverting the Migration (If Needed)
438 +If you want to move an app back to the old repository:
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.
440 +2. Enable the old ChartMuseum repo.
441 +3. Open the application → **Upgrade**.
442 +4. Select the chart from the old repo.
443 +5. Save.
426 426  
427 427  This will reconnect the app to the old repository.
428 428  
429 -=
430 -Automated deployments with Jenkins =
447 +---
431 431  
449 +## Summary
450 +- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
451 +- After upgrade, apps no longer track versions from the old repository.
452 +- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.
453 +
454 +---
455 +
456 +If you want, I can also generate:
457 +- a shorter version (1-pager),
458 +- a diagram,
459 +- a Rancher UI screenshot guide,
460 +- or a version tailored for your team’s internal wiki.
461 +
462 +
463 += Automated deployments with Jenkins =
464 +
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