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 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
-
... ... @@ -392,13 +392,12 @@ 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## 396 -##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.## 397 397 11. Go to **Apps → Repositories**. 398 398 11. Disable the old HTTP(S)-based repository. 399 399 11. Keep it disabled until the migration is done. 400 400 1. ##Update Existing Applications to Use the New OCI Repo## 401 -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.## 402 402 11. Go to **Apps → Installed Apps**. 403 403 11. Open the application that was deployed using the old repo. 404 404 11. Click **Upgrade**. ... ... @@ -405,26 +405,41 @@ 405 405 11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 406 406 11. Choose the chart version you want to deploy (same or newer). 407 407 11. Click **Upgrade**. 408 -1. ##Re-enable the Old Repository (Optional) ## 409 -If you still need the old repo for other apps, re-enable it after the migration steps above. 410 -**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.## 411 411 412 - ----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. 413 413 411 +----- 412 + 414 414 ## Reverting the Migration (If Needed) 415 415 If you want to move an app back to the old repository:## 416 416 417 417 1. Temporarily disable the new OCI repo. 418 - 1. Enable the old ChartMuseum repo.419 - 1. Open the application → **Upgrade**.420 - 1. Select the chart from the old repo.421 - 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. 422 422 423 423 This will reconnect the app to the old repository. 424 424 424 +----- 425 425 426 -Automated deployments with Jenkins 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.## 427 427 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 + 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 ==