Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From 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
To 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
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -392,12 +392,13 @@ 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.## 395 +1. ##Disable the Old ChartMuseum Repository Temporarily## 396 +##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. 399 399 1. ##Update Existing Applications to Use the New OCI Repo## 400 - ##Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.##401 +Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition. 401 401 11. Go to **Apps → Installed Apps**. 402 402 11. Open the application that was deployed using the old repo. 403 403 11. Click **Upgrade**. ... ... @@ -404,7 +404,9 @@ 404 404 11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 405 405 11. Choose the chart version you want to deploy (same or newer). 406 406 11. Click **Upgrade**. 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 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 408 408 409 409 ---- 410 410 ... ... @@ -419,24 +419,9 @@ 419 419 420 420 This will reconnect the app to the old repository. 421 421 422 ----- 423 423 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.## 426 +Automated deployments with Jenkins 428 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 - 440 440 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 441 441 442 442 == Prerequisites ==