Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 15.1
edited by Diana Strebkova
on 2025/12/12 13:38
on 2025/12/12 13:38
Change comment:
There is no comment for this version
To version 12.2
edited by Diana Strebkova
on 2025/12/12 12:25
on 2025/12/12 12:25
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,32 +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. 384 -This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can: 385 -1.* Create a new OCI repository for each chart, 386 -1.* Keep the old ChartMuseum repo enabled during the migration, 387 -1.* Migrate applications gradually following the steps described here. 388 - 389 -This avoids disruptions and allows controlled migration. 390 - 391 -Special Case: Old Repo Targeting Multiple Chart Repos 392 - 393 -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. 394 - 395 -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 396 - 397 397 (% class="box" %) 398 398 ((( 399 399 **We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** ... ... @@ -416,13 +416,12 @@ 416 416 11. Add a new repository of type **OCI**. 417 417 11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same. 418 418 11. Point it to the new OCI endpoint. 419 -1. ##Disable the Old ChartMuseum Repository Temporarily## 420 -##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.## 421 421 11. Go to **Apps → Repositories**. 422 422 11. Disable the old HTTP(S)-based repository. 423 423 11. Keep it disabled until the migration is done. 424 424 1. ##Update Existing Applications to Use the New OCI Repo## 425 -Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition. 400 +##Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.## 426 426 11. Go to **Apps → Installed Apps**. 427 427 11. Open the application that was deployed using the old repo. 428 428 11. Click **Upgrade**. ... ... @@ -429,9 +429,7 @@ 429 429 11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 430 430 11. Choose the chart version you want to deploy (same or newer). 431 431 11. Click **Upgrade**. 432 -1. ##Re-enable the Old Repository (Optional) ## 433 -If you still need the old repo for other apps, re-enable it after the migration steps above. 434 -**Note:** Even if a newer chart version exists in the old repository, your migrated app **will not see it**, because it is no longer connected to that repo 407 +1. ##Re-enable the Old Repository (Optional) If you still need the old repo for other apps, re-enable it after the migration steps above.##Note: Even if a newer chart version exists in the old repository, your migrated app **will not see it**, because it is no longer connected to that repo 435 435 436 436 ---- 437 437 ... ... @@ -446,9 +446,24 @@ 446 446 447 447 This will reconnect the app to the old repository. 448 448 449 -= 450 -Automated deployments with Jenkins = 422 +---- 451 451 424 +## Summary 425 +- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo. 426 +- After upgrade, apps no longer track versions from the old repository. 427 +- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.## 428 + 429 +---- 430 + 431 +If you want, I can also generate: 432 +- a shorter version (1-pager), 433 +- a diagram, 434 +- a Rancher UI screenshot guide, 435 +- or a version tailored for your team’s internal wiki. 436 + 437 + 438 += Automated deployments with Jenkins = 439 + 452 452 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 453 453 454 454 == Prerequisites ==