Skip to Content

Changes for page Rancher 2

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

Summary

Details

Page properties
Content
... ... @@ -281,7 +281,6 @@
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" %)
285 285  
286 286  [[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"]]
287 287  
... ... @@ -336,7 +336,6 @@
336 336  (% class="wikigeneratedid" %)
337 337  Click Create.
338 338  
339 -
340 340  (% class="wrapped" %)
341 341  |=(((
342 342  Field
... ... @@ -363,10 +363,76 @@
363 363  {{/info}}
364 364  )))
365 365  
366 -=== Migrating ===
364 +=== Migrating chart repositories in rancher to new OCI Repository format ===
367 367  
368 -= Automated deployments with Jenkins =
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 +)))
369 369  
371 +There are 2 ways to "migrate" the repos:
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 +(% class="box" %)
380 +(((
381 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
382 +)))
383 +
384 +| Term | Meaning
385 +| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
386 +| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
387 +
388 +##__**Why This Migration Is Required:**__##
389 +
390 +* ##ChartMuseum is deprecated and will be removed.##
391 +* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
392 +* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
393 +
394 +## Migration Steps:##
395 +
396 +1. ##Create the New OCI Repository in Rancher##
397 +11. Go to **Apps → Repositories**.
398 +11. Add a new repository of type **OCI**.
399 +11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
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.##
403 +11. Go to **Apps → Repositories**.
404 +11. Disable the old HTTP(S)-based repository.
405 +11. Keep it disabled until the migration is done.
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.
408 +11. Go to **Apps → Installed Apps**.
409 +11. Open the application that was deployed using the old repo.
410 +11. Click **Upgrade**.
411 +11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
412 +11. Choose the chart version you want to deploy (same or newer).
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
417 +
418 +----
419 +
420 +## Reverting the Migration (If Needed)
421 +If you want to move an app back to the old repository:##
422 +
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.
428 +
429 +This will reconnect the app to the old repository.
430 +
431 +=
432 +Automated deployments with Jenkins =
433 +
370 370  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
371 371  
372 372  == Prerequisites ==
© 2018-2025 T-Systems International GmbH