Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 15.3
edited by Diana Strebkova
on 2025/12/12 13:55
on 2025/12/12 13:55
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,28 +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 are twoways tomigrateyourrepositories: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. ##Direct Transition (Editing the Existing Repository)## 374 -1*. Change the target to “OCI Repository”. 375 -1*. Update the URL as required (the repository name cannot be changed). 376 -1*. After saving, installed apps will automatically start using the updated repository. 377 -1*. (% class="box" %) 378 -((( 379 -Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder. 380 -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”). 381 -The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart. 382 -))) 383 -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: 384 -1*. Create a new OCI repository for each chart, 385 -1*. Keep the old ChartMuseum repo enabled during the migration, 386 -1*. Migrate applications gradually following the steps described here. 387 -1*. This avoids disruptions and allows controlled migration. 388 -1. //Special Case: Old Repo Targeting Multiple Chart Repos// 389 -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. 390 - 391 -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 392 - 393 393 (% class="box" %) 394 394 ((( 395 395 **We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** ... ... @@ -412,8 +412,7 @@ 412 412 11. Add a new repository of type **OCI**. 413 413 11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same. 414 414 11. Point it to the new OCI endpoint. 415 -1. ##Disable the Old ChartMuseum Repository Temporarily## 416 -##This step ensures that Rancher resolves charts from the new OCI repo.## 395 +1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.## 417 417 11. Go to **Apps → Repositories**. 418 418 11. Disable the old HTTP(S)-based repository. 419 419 11. Keep it disabled until the migration is done. ... ... @@ -442,9 +442,9 @@ 442 442 443 443 This will reconnect the app to the old repository. 444 444 445 -= 446 -Automated deployments with Jenkins = 447 447 425 +Automated deployments with Jenkins 426 + 448 448 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 449 449 450 450 == Prerequisites ==