Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From 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
To version 11.1
edited by Diana Strebkova
on 2025/12/12 12:08
on 2025/12/12 12:08
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -281,6 +281,7 @@ 281 281 (% class="p1" %) 282 282 In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu. 283 283 284 +(% class="p1" %) 284 284 285 285 [[image:attach:Screenshot 2023-04-25 at 13.11.48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="400" width="209"]] 286 286 ... ... @@ -364,55 +364,54 @@ 364 364 365 365 === Migrating chart repositories in rancher to new OCI Repository format === 366 366 367 - (%class="wikigeneratedid"%)368 +# Migration Guide: ChartMuseum → OCI-based Chart Repositories in Rancher 368 368 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)**.## 370 +## Overview 371 +ChartMuseum is being deprecated. After the migration is complete, **all charts will be removed from ChartMuseum**, and **old HTTP(S)-based chart repositories will no longer work in Rancher**. 370 370 371 -To ensure a smooth transition, we recomment should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.373 +To ensure a smooth transition, each project should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. 372 372 373 373 We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. 374 374 375 ---- --377 +--- 376 376 377 -## Terminology## 379 +## Terminology 380 +| Term | Meaning | 381 +|------|---------| 382 +| **Old Repository** | The existing HTTP/HTTPS ChartMuseum repository. | 383 +| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). | 378 378 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`). | 385 +--- 383 383 384 ------ 385 - 386 386 ## Why This Migration Is Required 387 387 - ChartMuseum is deprecated and will be removed. 388 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**. ##390 +- Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions**. 390 390 391 ---- --392 +--- 392 392 393 -## Migration Steps ##394 +## Migration Steps 394 394 395 -### 1. Create the New OCI Repository in Rancher## 396 - 396 +### 1. Create the New OCI Repository in Rancher 397 397 1. Go to **Apps → Repositories**. 398 398 2. Add a new repository of type **OCI**. 399 399 3. Name it exactly like your old repo name (e.g. `<chart-repo-name>`). 400 400 4. Point it to the new OCI endpoint. 401 401 402 ---- --402 +--- 403 403 404 404 ### 2. Disable the Old ChartMuseum Repository Temporarily 405 -This step ensures that Rancher resolves charts from the new OCI repo. ##405 +This step ensures that Rancher resolves charts from the new OCI repo. 406 406 407 407 1. Go to **Apps → Repositories**. 408 408 2. Disable the old HTTP(S)-based repository. 409 409 3. Keep it disabled until the migration is done. 410 410 411 ---- --411 +--- 412 412 413 413 ### 3. Update Existing Applications to Use the New OCI Repo 414 414 Applications deployed with the old repository still contain the old repo name in their metadata. 415 -You must upgrade them once to transition. ##415 +You must upgrade them once to transition. 416 416 417 417 1. Go to **Apps → Installed Apps**. 418 418 2. Open the application that was deployed using the old repo. ... ... @@ -425,18 +425,17 @@ 425 425 - Your application is now linked to the **new OCI repository**. 426 426 - Rancher will show upgrade notifications only for versions available in the new repo. 427 427 428 ---- --428 +--- 429 429 430 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. ##431 +If you still need the old repo for other apps, re-enable it after the migration steps above. 432 432 433 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 434 435 ---- --435 +--- 436 436 437 437 ## Reverting the Migration (If Needed) 438 -If you want to move an app back to the old repository:## 439 - 438 +If you want to move an app back to the old repository: 440 440 1. Temporarily disable the new OCI repo. 441 441 2. Enable the old ChartMuseum repo. 442 442 3. Open the application → **Upgrade**. ... ... @@ -445,14 +445,14 @@ 445 445 446 446 This will reconnect the app to the old repository. 447 447 448 ---- --447 +--- 449 449 450 450 ## Summary 451 451 - Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo. 452 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. ##452 +- Old repository will stop functioning after ChartMuseum shutdown, so migration is required. 454 454 455 ---- --454 +--- 456 456 457 457 If you want, I can also generate: 458 458 - a shorter version (1-pager),