Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.3
edited by Diana Strebkova
on 2025/12/12 12:26
on 2025/12/12 12:26
Change comment:
There is no comment for this version
To version 12.15
edited by Diana Strebkova
on 2025/12/12 13:22
on 2025/12/12 13:22
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,37 @@ 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**addan OCI-basedrepositoryalongside the existingChartMuseumrepository** during themigration phase.371 +There are two ways to migrate your repositories: 372 372 373 +1. Direct Transition (Editing the Existing Repository) 374 + You can modify the existing repository directly: 375 +Change the target to “OCI Repository”. 376 + 377 +* Update the URL as required (the repository name cannot be changed). 378 + 379 +After saving, installed apps will automatically start using the updated repository. 380 + 381 +Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder. 382 +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”). 383 +The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart. 384 + 385 +1. Add New Repositories One by One (Recommended) 386 + 387 +This approach allows a smooth transition while the old ChartMuseum repository continues to function. 388 +You can: 389 + 390 +* Create a new OCI repository for each chart, 391 +* Keep the old ChartMuseum repo enabled during the migration, 392 +* Migrate applications gradually following the steps described in the main migration guide. 393 + 394 +This avoids disruptions and allows controlled migration. 395 + 396 +Special Case: Old Repo Targeting Multiple Chart Repos 397 + 398 +If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please contact support. OCI does not support multi-chart endpoints within a single repository, and we can help you find an appropriate solution. 399 + 400 +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 401 + 373 373 (% class="box" %) 374 374 ((( 375 375 **We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** ... ... @@ -392,7 +392,8 @@ 392 392 11. Add a new repository of type **OCI**. 393 393 11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same. 394 394 11. Point it to the new OCI endpoint. 395 -1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.## 424 +1. ##Disable the Old ChartMuseum Repository Temporarily## 425 +##This step ensures that Rancher resolves charts from the new OCI repo.## 396 396 11. Go to **Apps → Repositories**. 397 397 11. Disable the old HTTP(S)-based repository. 398 398 11. Keep it disabled until the migration is done. ... ... @@ -421,9 +421,9 @@ 421 421 422 422 This will reconnect the app to the old repository. 423 423 454 += 455 +Automated deployments with Jenkins = 424 424 425 -Automated deployments with Jenkins 426 - 427 427 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 428 428 429 429 == Prerequisites ==