Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.12
edited by Diana Strebkova
on 2025/12/12 13:16
on 2025/12/12 13:16
Change comment:
There is no comment for this version
To version 11.3
edited by Diana Strebkova
on 2025/12/12 12:23
on 2025/12/12 12:23
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,13 +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 are2ways"migrate"the repos: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. You can do direct transition and edit already existing repository – choose //Target: OCI repository, //adapt the url as shown above (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The issue is that the OCI repository needs to target chart repos in the url, not the whole folder anymore. That means if you previously deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket", you will still need to create a new repo targeting "jira". 374 -1. Or you can add new repositories one by 375 - 376 -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 377 - 378 378 (% class="box" %) 379 379 ((( 380 380 **We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** ... ... @@ -397,13 +397,12 @@ 397 397 11. Add a new repository of type **OCI**. 398 398 11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same. 399 399 11. Point it to the new OCI endpoint. 400 -1. ##Disable the Old ChartMuseum Repository Temporarily## 401 -##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.## 402 402 11. Go to **Apps → Repositories**. 403 403 11. Disable the old HTTP(S)-based repository. 404 404 11. Keep it disabled until the migration is done. 405 405 1. ##Update Existing Applications to Use the New OCI Repo## 406 -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.## 407 407 11. Go to **Apps → Installed Apps**. 408 408 11. Open the application that was deployed using the old repo. 409 409 11. Click **Upgrade**. ... ... @@ -410,26 +410,41 @@ 410 410 11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 411 411 11. Choose the chart version you want to deploy (same or newer). 412 412 11. Click **Upgrade**. 413 -1. ##Re-enable the Old Repository (Optional) ## 414 -If you still need the old repo for other apps, re-enable it after the migration steps above. 415 -**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.## 416 416 417 - ----409 + 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. 418 418 411 +----- 412 + 419 419 ## Reverting the Migration (If Needed) 420 420 If you want to move an app back to the old repository:## 421 421 422 422 1. Temporarily disable the new OCI repo. 423 - 1. Enable the old ChartMuseum repo.424 - 1. Open the application → **Upgrade**.425 - 1. Select the chart from the old repo.426 - 1. Save.417 +2. Enable the old ChartMuseum repo. 418 +3. Open the application → **Upgrade**. 419 +4. Select the chart from the old repo. 420 +5. Save. 427 427 428 428 This will reconnect the app to the old repository. 429 429 430 -= 431 -Automated deployments with Jenkins = 424 +----- 432 432 426 +## Summary 427 +- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo. 428 +- After upgrade, apps no longer track versions from the old repository. 429 +- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.## 430 + 431 +----- 432 + 433 +If you want, I can also generate: 434 +- a shorter version (1-pager), 435 +- a diagram, 436 +- a Rancher UI screenshot guide, 437 +- or a version tailored for your team’s internal wiki. 438 + 439 + 440 += Automated deployments with Jenkins = 441 + 433 433 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 434 434 435 435 == Prerequisites ==