Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.14
edited by Diana Strebkova
on 2025/12/12 13:20
on 2025/12/12 13:20
Change comment:
There is no comment for this version
To version 12.3
edited by Diana Strebkova
on 2025/12/12 12:26
on 2025/12/12 12:26
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -368,14 +368,8 @@ 368 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 ))) 370 370 371 -T here are2ways"migrate"the repos: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 -1. You can do direct transition and edit already existing repository – choose //Target: OCI repository, //adapt the url as shown above (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The issue is that the OCI repository needs to target chart repos in the url, not the whole folder anymore. That means if you previously deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket", other repos updates wont be working anymore and you will still need to create a new repo targeting each chartrepo. 374 -1. Or you can add new repositories one by one taking your time, while the old chartmuseum repo will still be functioning suring migraiton. For this, you can see the next described migration process. 375 -1. If you have a repo targeting multiple repos and need that the new OCI repo behaves as the previous one, please contact support for finding out the solution. 376 - 377 -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 378 - 379 379 (% class="box" %) 380 380 ((( 381 381 **We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.** ... ... @@ -398,8 +398,7 @@ 398 398 11. Add a new repository of type **OCI**. 399 399 11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same. 400 400 11. Point it to the new OCI endpoint. 401 -1. ##Disable the Old ChartMuseum Repository Temporarily## 402 -##This step ensures that Rancher resolves charts from the new OCI repo.## 395 +1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.## 403 403 11. Go to **Apps → Repositories**. 404 404 11. Disable the old HTTP(S)-based repository. 405 405 11. Keep it disabled until the migration is done. ... ... @@ -428,9 +428,9 @@ 428 428 429 429 This will reconnect the app to the old repository. 430 430 431 -= 432 -Automated deployments with Jenkins = 433 433 425 +Automated deployments with Jenkins 426 + 434 434 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins. 435 435 436 436 == Prerequisites ==