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 15.4
edited by Diana Strebkova
on 2025/12/12 13:56
on 2025/12/12 13:56
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,33 @@ 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 -To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. 371 +(% class="box" %) 372 +((( 373 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. After m** 374 +))) 372 372 376 +There are two ways to migrate your repositories: 377 + 378 +1. ##Direct Transition (Editing the Existing Repository)## 379 +1*. Change the target to “OCI Repository”. 380 +1*. Update the URL as required (the repository name cannot be changed). 381 +1*. After saving, installed apps will automatically start using the updated repository. 382 +1*. (% class="box" %) 383 +((( 384 +Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder. 385 +If your old repository included several charts (for example “bitbucket” and “jira”), then after switching to OCI you can only target one chart (e.g. “bitbucket”). 386 +The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart. 387 +))) 388 +1. Add New Repositories One by One (Recommended), preserve the old one till the end. This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can: 389 +1*. Create a new OCI repository for each chart, 390 +1*. Keep the old ChartMuseum repo enabled during the migration, 391 +1*. Migrate applications gradually following the steps described here. 392 +1*. This avoids disruptions and allows controlled migration. 393 +1. //Special Case: Old Repo Targeting Multiple Chart Repos// 394 +If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.** 395 + 396 +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 397 + 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 450 += 451 +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 ==