Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 10.10
edited by Diana Strebkova
on 2025/12/12 11:55
Change comment: There is no comment for this version
To version 12.8
edited by Diana Strebkova
on 2025/12/12 13:05
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  
... ... @@ -316,7 +316,7 @@
316 316  ==== Target: OCI Repository ====
317 317  
318 318  {{info}}
319 -Now all internal helm charts are stored in harbor folders with -helm suffix. Adding the whole public project doesn't work natively anymore, so each separate chart should be added as a separate repo.//** If you have a real need to add the whole project, please contact support for finding a possible solution.**//
318 +Now all internal helm charts are stored in harbor folders with -helm suffix. Adding the whole public project doesn't work natively anymore, so each separate chart should be added as a separate repo.//** If you have a real need to add the whole project, please contact support for finding a possible solution.**//
320 320  {{/info}}
321 321  
322 322  (% class="p1" %)
... ... @@ -336,7 +336,6 @@
336 336  (% class="wikigeneratedid" %)
337 337  Click Create.
338 338  
339 -
340 340  (% class="wrapped" %)
341 341  |=(((
342 342  Field
... ... @@ -346,27 +346,91 @@
346 346  |=(((
347 347  Name
348 348  )))|(((
349 -devopsaas-jenkins-auto-agent
347 +sdcloud-sdportal
350 350  )))
351 351  |=(((
352 352  Description
353 353  )))|(((
354 -Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
352 +Sdportal charts of sdcloud project
355 355  )))
356 356  |=(((
357 357  Index URL
358 358  )))|(((
359 -oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
357 +oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
360 360  
361 -oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
362 -
363 363  {{info}}
364 -Take into account, that all internal harbor repositories with helm charts have PKEY-helm naming convention, adding repo with both docker images and helm charts may not be supported in rancher.
360 +Now we should target a chart repo directly, not the whole project. In you need to reference the whole project with a lot of repos, please contact support to find a possible solution.
365 365  {{/info}}
366 366  )))
367 367  
368 -= Automated deployments with Jenkins =
364 +=== Migrating chart repositories in rancher to new OCI Repository format ===
369 369  
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 +)))
370 +
371 +There are 2 ways to "migrate" the repos:
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
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
376 +
377 +(% class="box" %)
378 +(((
379 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
380 +)))
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`).
385 +
386 +##__**Why This Migration Is Required:**__##
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**.##
391 +
392 +## Migration Steps:##
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
415 +
416 +----
417 +
418 +## Reverting the Migration (If Needed)
419 +If you want to move an app back to the old repository:##
420 +
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.
426 +
427 +This will reconnect the app to the old repository.
428 +
429 +=
430 +Automated deployments with Jenkins =
431 +
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