Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23

From 13.1 to 14.1 From 20.1 to 21.1

From version 14.1

edited by Diana Strebkova
on 2025/12/12 13:32

Change comment: There is no comment for this version

To version 20.1

edited by Diana Strebkova
on 2025/12/12 14:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 3 added, 0 removed)

Details

Page properties

Content

@@ -249,9 +249,9 @@
  oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
--{{info}}
--Take into account, that all internal harbor repositories with helm charts have PKEY-helm naming convention, adding repo with both docker images and helm charts may not be supported in rancher.
--{{/info}}
++{{box}}
++Take into account, that all internal harbor repositories with helm charts have PKEY-helm naming convention, adding repo with both docker images and helm charts is not supported in rancher.
++{{/box}}
  )))
  {{info}}
@@ -287,8 +287,8 @@
  (% class="p1" %)
  Create a new Repository by pressing the Create button.
--(% id="HTarget:http28s29URL-1" class="p1" %)
--==== [[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]] ====
++(% class="p1" id="HTarget:http28s29URL-1" %)
++[[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]]
  (% id="HTarget:http28s29URL-1" class="p1" %)
  ==== Target: http(s) URL ====
@@ -368,43 +368,33 @@
  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)**.
  )))
++(% class="box" %)
++(((
++**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. During migration, please adapt your helm push commands and url's for new oci-compatible repository.**
++)))
++
  There are two ways to migrate your repositories:
 . ##Direct Transition (Editing the Existing Repository)##
--11. Change the target to “OCI Repository”.
--11. Update the URL as required (the repository name cannot be changed).
--
--1. Direct Transition (Editing the Existing Repository).You can modify the existing repository directly:
--Change the target to “OCI Repository”.Update the URL as required (the repository name cannot be changed).
--
--After saving, installed apps will automatically start using the updated repository.
--
++1*. Change the target to “OCI Repository”.
++1*. Update the URL as required (the repository name cannot be changed).
++1*. After saving, installed apps will automatically start using the updated repository.
++1*. (% class="box" %)
++(((
  Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
  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”).
  The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
++)))
++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:
++1*. Create a new OCI repository for each chart,
++1*. Keep the old ChartMuseum repo enabled during the migration,
++1*. Migrate applications gradually following the steps described here.
++1*. This avoids disruptions and allows controlled migration.
++1. //Special Case: Old Repo Targeting Multiple Chart Repos//
++If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
--1. Add New Repositories One by One (Recommended)
--
--This approach allows a smooth transition while the old ChartMuseum repository continues to function.
--You can:
--
--* Create a new OCI repository for each chart,
--* Keep the old ChartMuseum repo enabled during the migration,
--* Migrate applications gradually following the steps described in the main migration guide.
--
--This avoids disruptions and allows controlled migration.
--
--Special Case: Old Repo Targeting Multiple Chart Repos
--
--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.
--
  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
--(% class="box" %)
--(((
--**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
--)))
--
  | Term | Meaning
  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
@@ -420,7 +420,7 @@
 . ##Create the New OCI Repository in Rancher##
 . Go to **Apps → Repositories**.
 . Add a new repository of type **OCI**.
--11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
++11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). __**You can't name it the same and can't rename it later.**__
 . Point it to the new OCI endpoint.
 . ##Disable the Old ChartMuseum Repository Temporarily##
  ##This step ensures that Rancher resolves charts from the new OCI repo.##
@@ -427,12 +427,15 @@
 . Go to **Apps → Repositories**.
 . Disable the old HTTP(S)-based repository.
 . Keep it disabled until the migration is done.
++[[image:1765548124989-482.59.06.png||height="152" width="485"]]
 . ##Update Existing Applications to Use the New OCI Repo##
  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
 . Go to **Apps → Installed Apps**.
 . Open the application that was deployed using the old repo.
--11. Click **Upgrade**.
--11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
++11. Click **Edit/Upgrade**.
++[[image:1765548598644-830.png||height="138" width="811"]]
++11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. Or enter the chart name in search bar:
++[[image:1765548750604-334.png||height="293" width="308"]]
 . Choose the chart version you want to deploy (same or newer).
 . Click **Upgrade**.
 . ##Re-enable the Old Repository (Optional) ##
@@ -439,9 +439,7 @@
  If you still need the old repo for other apps, re-enable it after the migration steps above.
  **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
------
--
--## Reverting the Migration (If Needed)
++##
  If you want to move an app back to the old repository:##
 . Temporarily disable the new OCI repo.

1765548124989-482.59.06.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.dianastrebkovat-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+64.4 KB

Content

1765548598644-830.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.dianastrebkovat-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+153.4 KB

Content

1765548750604-334.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.dianastrebkovat-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+103.0 KB

Content

Changes for page Rancher 2

Summary

Details

DevOps-as-a-Service

Navigation