Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 14.3
edited by Diana Strebkova
on 2025/12/12 13:37
on 2025/12/12 13:37
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,93 +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), prese 384 -This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can: 371 +To ensure a smooth transition, we recomment should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. 385 385 386 -* Create a new OCI repository for each chart, 387 -* Keep the old ChartMuseum repo enabled during the migration, 388 -* Migrate applications gradually following the steps described in the main migration guide. 373 +We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. 389 389 390 - This avoids disruptions and allows controlled migration.375 +----- 391 391 392 - SpecialCase: Old RepoTargeting Multiple Chart Repos377 +## Terminology## 393 393 394 -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. 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 - 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 w384 +----- 397 397 398 - (%class="box"%)399 - (((400 - **Wewillmakeyourchartsavailablein thecorresponding new`<pkey>-helm` OCI projects.**401 - )))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**.## 402 402 403 -| Term | Meaning 404 -| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository. 405 -| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). 391 +----- 406 406 407 -## __**WhyThisMigrationIs Required:**__##393 +## Migration Steps## 408 408 409 -* ##ChartMuseum is deprecated and will be removed.## 410 -* ##Applications deployed from old repos keep a reference to that repo inside their labels.## 411 -* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.## 395 +### 1. Create the New OCI Repository in Rancher## 412 412 413 -## Migration Steps:## 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. 414 414 415 -1. ##Create the New OCI Repository in Rancher## 416 -11. Go to **Apps → Repositories**. 417 -11. Add a new repository of type **OCI**. 418 -11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same. 419 -11. Point it to the new OCI endpoint. 420 -1. ##Disable the Old ChartMuseum Repository Temporarily## 421 -##This step ensures that Rancher resolves charts from the new OCI repo.## 422 -11. Go to **Apps → Repositories**. 423 -11. Disable the old HTTP(S)-based repository. 424 -11. Keep it disabled until the migration is done. 425 -1. ##Update Existing Applications to Use the New OCI Repo## 426 -Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition. 427 -11. Go to **Apps → Installed Apps**. 428 -11. Open the application that was deployed using the old repo. 429 -11. Click **Upgrade**. 430 -11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 431 -11. Choose the chart version you want to deploy (same or newer). 432 -11. Click **Upgrade**. 433 -1. ##Re-enable the Old Repository (Optional) ## 434 -If you still need the old repo for other apps, re-enable it after the migration steps above. 435 -**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 402 +----- 436 436 437 ----- 404 +### 2. Disable the Old ChartMuseum Repository Temporarily 405 +This step ensures that Rancher resolves charts from the new OCI repo.## 438 438 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 + 439 439 ## Reverting the Migration (If Needed) 440 440 If you want to move an app back to the old repository:## 441 441 442 442 1. Temporarily disable the new OCI repo. 443 - 1. Enable the old ChartMuseum repo.444 - 1. Open the application → **Upgrade**.445 - 1. Select the chart from the old repo.446 - 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. 447 447 448 448 This will reconnect the app to the old repository. 449 449 450 -= 451 -Automated deployments with Jenkins = 448 +----- 452 452 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 + 453 453 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 454 454 455 455 == Prerequisites ==