Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From 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
To version 12.1
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
-
... ... @@ -281,7 +281,6 @@ 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" %) 285 285 286 286 [[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"]] 287 287 ... ... @@ -336,7 +336,6 @@ 336 336 (% class="wikigeneratedid" %) 337 337 Click Create. 338 338 339 - 340 340 (% class="wrapped" %) 341 341 |=((( 342 342 Field ... ... @@ -365,77 +365,56 @@ 365 365 366 366 === Migrating chart repositories in rancher to new OCI Repository format === 367 367 368 -# Migration Guide: ChartMuseum → OCI-based Chart Repositories in Rancher 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 +))) 369 369 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**. 371 +To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. 372 372 373 -To ensure a smooth transition, each project should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. 373 +(% class="box" %) 374 +((( 375 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** 376 +))) 374 374 375 -We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. 378 +| Term | Meaning 379 +| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository. 380 +| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). 376 376 377 - ---382 +##__**Why This Migration Is Required:**__## 378 378 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`). | 384 +* ##ChartMuseum is deprecated and will be removed.## 385 +* ##Applications deployed from old repos keep a reference to that repo inside their labels.## 386 +* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.## 384 384 385 - ---388 +## Migration Steps:## 386 386 387 -## Why This Migration Is Required 388 -- ChartMuseum is deprecated and will be removed. 389 -- Applications deployed from old repos keep a reference to that repo inside their labels. 390 -- Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions**. 390 +1. ##Create the New OCI Repository in Rancher## 391 +11. Go to **Apps → Repositories**. 392 +11. Add a new repository of type **OCI**. 393 +11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same. 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.## 396 +11. Go to **Apps → Repositories**. 397 +11. Disable the old HTTP(S)-based repository. 398 +11. Keep it disabled until the migration is done. 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 +11. Go to **Apps → Installed Apps**. 402 +11. Open the application that was deployed using the old repo. 403 +11. Click **Upgrade**. 404 +11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. 405 +11. Choose the chart version you want to deploy (same or newer). 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.## 391 391 392 - ---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. 393 393 394 - ## Migration Steps411 +----- 395 395 396 -### 1. Create the New OCI Repository in Rancher 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. 401 - 402 ---- 403 - 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 -If you want to move an app back to the old repository: 414 +If you want to move an app back to the old repository:## 415 + 439 439 1. Temporarily disable the new OCI repo. 440 440 2. Enable the old ChartMuseum repo. 441 441 3. Open the application → **Upgrade**. ... ... @@ -444,14 +444,14 @@ 444 444 445 445 This will reconnect the app to the old repository. 446 446 447 ---- 424 +----- 448 448 449 449 ## Summary 450 450 - Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo. 451 451 - After upgrade, apps no longer track versions from the old repository. 452 -- Old repository will stop functioning after ChartMuseum shutdown, so migration is required. 429 +- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.## 453 453 454 ---- 431 +----- 455 455 456 456 If you want, I can also generate: 457 457 - a shorter version (1-pager),