Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 15.2
edited by Diana Strebkova
on 2025/12/12 13:40
on 2025/12/12 13:40
Change comment:
There is no comment for this version
To version 11.2
edited by Diana Strebkova
on 2025/12/12 12:09
on 2025/12/12 12:09
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -335,6 +335,7 @@ 335 335 (% class="wikigeneratedid" %) 336 336 Click Create. 337 337 338 + 338 338 (% class="wrapped" %) 339 339 |=((( 340 340 Field ... ... @@ -363,91 +363,105 @@ 363 363 364 364 === Migrating chart repositories in rancher to new OCI Repository format === 365 365 366 -(% class="box warningmessage" %) 367 -((( 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 -))) 367 +(% class="wikigeneratedid" %) 370 370 371 - There are twoways tomigrateyour repositories:369 +##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)**.## 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. 371 +To ensure a smooth transition, we recomment should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. 387 387 388 - Thisavoidsdisruptions andallowscontrolledmigration.373 +We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. 389 389 390 - Special Case: Old Repo Targeting Multiple Chart Repos375 +----- 391 391 392 - Ifyourexistingrepository targetsmultiple 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.377 +## Terminology## 393 393 394 -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 379 +| Term | Meaning | 380 +| |-| 381 +| **Old Repository** | The existing HTTP/HTTPS ChartMuseum repository. | 382 +| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). | 395 395 396 -(% class="box" %) 397 -((( 398 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** 399 -))) 384 +----- 400 400 401 -| Term | Meaning 402 -| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository. 403 -| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). 386 +## Why This Migration Is Required 387 +- ChartMuseum is deprecated and will be removed. 388 +- Applications deployed from old repos keep a reference to that repo inside their labels. 389 +- Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions**.## 404 404 405 - ##__**Why This Migration Is Required:**__##391 +----- 406 406 407 -* ##ChartMuseum is deprecated and will be removed.## 408 -* ##Applications deployed from old repos keep a reference to that repo inside their labels.## 409 -* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.## 393 +## Migration Steps## 410 410 411 -## MigrationSteps:##395 +### 1. Create the New OCI Repository in Rancher## 412 412 413 -1. ##Create the New OCI Repository in Rancher## 414 -11. Go to **Apps → Repositories**. 415 -11. Add a new repository of type **OCI**. 416 -11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same. 417 -11. Point it to the new OCI endpoint. 418 -1. ##Disable the Old ChartMuseum Repository Temporarily## 419 -##This step ensures that Rancher resolves charts from the new OCI repo.## 420 -11. Go to **Apps → Repositories**. 421 -11. Disable the old HTTP(S)-based repository. 422 -11. Keep it disabled until the migration is done. 423 -1. ##Update Existing Applications to Use the New OCI Repo## 424 -Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition. 425 -11. Go to **Apps → Installed Apps**. 426 -11. Open the application that was deployed using the old repo. 427 -11. Click **Upgrade**. 428 -11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 429 -11. Choose the chart version you want to deploy (same or newer). 430 -11. Click **Upgrade**. 431 -1. ##Re-enable the Old Repository (Optional) ## 432 -If you still need the old repo for other apps, re-enable it after the migration steps above. 433 -**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 397 +1. Go to **Apps → Repositories**. 398 +2. Add a new repository of type **OCI**. 399 +3. Name it exactly like your old repo name (e.g. `<chart-repo-name>`). 400 +4. Point it to the new OCI endpoint. 434 434 435 ----- 402 +----- 436 436 404 +### 2. Disable the Old ChartMuseum Repository Temporarily 405 +This step ensures that Rancher resolves charts from the new OCI repo.## 406 + 407 +1. Go to **Apps → Repositories**. 408 +2. Disable the old HTTP(S)-based repository. 409 +3. Keep it disabled until the migration is done. 410 + 411 +----- 412 + 413 +### 3. Update Existing Applications to Use the New OCI Repo 414 +Applications deployed with the old repository still contain the old repo name in their metadata. 415 +You must upgrade them once to transition.## 416 + 417 +1. Go to **Apps → Installed Apps**. 418 +2. Open the application that was deployed using the old repo. 419 +3. Click **Upgrade**. 420 +4. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 421 +5. Choose the chart version you want to deploy (same or newer). 422 +6. Click **Upgrade**. 423 + 424 +After this upgrade: 425 +- Your application is now linked to the **new OCI repository**. 426 +- Rancher will show upgrade notifications only for versions available in the new repo. 427 + 428 +----- 429 + 430 +### 4. Re-enable the Old Repository (Optional) 431 +If you still need the old repo for other apps, re-enable it after the migration steps above.## 432 + 433 +> 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. 434 + 435 +----- 436 + 437 437 ## Reverting the Migration (If Needed) 438 438 If you want to move an app back to the old repository:## 439 439 440 440 1. Temporarily disable the new OCI repo. 441 - 1. Enable the old ChartMuseum repo.442 - 1. Open the application → **Upgrade**.443 - 1. Select the chart from the old repo.444 - 1. Save.441 +2. Enable the old ChartMuseum repo. 442 +3. Open the application → **Upgrade**. 443 +4. Select the chart from the old repo. 444 +5. Save. 445 445 446 446 This will reconnect the app to the old repository. 447 447 448 -= 449 -Automated deployments with Jenkins = 448 +----- 450 450 450 +## Summary 451 +- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo. 452 +- After upgrade, apps no longer track versions from the old repository. 453 +- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.## 454 + 455 +----- 456 + 457 +If you want, I can also generate: 458 +- a shorter version (1-pager), 459 +- a diagram, 460 +- a Rancher UI screenshot guide, 461 +- or a version tailored for your team’s internal wiki. 462 + 463 + 464 += Automated deployments with Jenkins = 465 + 451 451 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 452 452 453 453 == Prerequisites ==