Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.12
edited by Diana Strebkova
on 2025/12/12 13:16
on 2025/12/12 13:16
Change comment:
There is no comment for this version
To version 12.4
edited by Diana Strebkova
on 2025/12/12 12:27
on 2025/12/12 12:27
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,13 +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 -T here are2ways"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", you will still need to create a new repo targeting "jira". 374 -1. Or you can add new repositories one by 375 - 376 -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 377 - 378 378 (% class="box" %) 379 379 ((( 380 380 **We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** ... ... @@ -427,9 +427,9 @@ 427 427 428 428 This will reconnect the app to the old repository. 429 429 430 -= 431 -Automated deployments with Jenkins = 432 432 426 +Automated deployments with Jenkins 427 + 433 433 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 434 434 435 435 == Prerequisites ==