Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From 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
To version 12.9
edited by Diana Strebkova
on 2025/12/12 13:10
on 2025/12/12 13:10
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,8 +368,12 @@ 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 oensure asmooth transition, werecommendto **add an OCI-basedrepositoryalongsidetheexisting ChartMuseumrepository** during the migration phase.371 +There are 2 ways to "migrate" the repos: 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" 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 + 373 373 (% class="box" %) 374 374 ((( 375 375 **We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** ... ... @@ -422,9 +422,9 @@ 422 422 423 423 This will reconnect the app to the old repository. 424 424 429 += 430 +Automated deployments with Jenkins = 425 425 426 -Automated deployments with Jenkins 427 - 428 428 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 429 429 430 430 == Prerequisites ==