Changes for page Rancher 2

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

From 10.12 to 10.11 From 17.1 to 16.2

From version 16.2

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

Change comment: There is no comment for this version

To version 10.12

edited by Diana Strebkova
on 2025/12/12 11:58

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- 1765548124989-482.59.06.png

Details

Page properties

Content

@@ -281,6 +281,7 @@
  (% class="p1" %)
  In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
++(% class="p1" %)
  [[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"]]
@@ -335,6 +335,7 @@
  (% class="wikigeneratedid" %)
  Click Create.
++
  (% class="wrapped" %)
  |=(((
  Field
@@ -361,91 +361,10 @@
  {{/info}}
  )))
--=== Migrating chart repositories in rancher to new OCI Repository format ===
++=== Migrating  ===
--(% class="box warningmessage" %)
--(((
--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)**.
--)))
++= Automated deployments with Jenkins =
--(% 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:
--
--1. ##Direct Transition (Editing the Existing 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.**
--
--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
--
--| 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`).
--
--##__**Why This Migration Is Required:**__##
--
--* ##ChartMuseum is deprecated and will be removed.##
--* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
--* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
--
--## Migration Steps:##
--
--1. ##Create the New OCI Repository in Rancher##
--11. Go to **Apps → Repositories**.
--11. 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. Point it to the new OCI endpoint.
--1. ##Disable the Old ChartMuseum Repository Temporarily##
--##This step ensures that Rancher resolves charts from the new OCI repo.##
--11. Go to **Apps → Repositories**.
--11. Disable the old HTTP(S)-based repository.
--11. Keep it disabled until the migration is done.
--[[image:1765548124989-482.59.06.png||height="152" width="485"]]
--1. ##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.
--11. Go to **Apps → Installed Apps**.
--11. Open the application that was deployed using the old repo.
--11. Click **Edit/Upgrade**.
--11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
--11. Choose the chart version you want to deploy (same or newer).
--11. Click **Upgrade**.
--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.
--**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:##
--
--1. Temporarily disable the new OCI repo.
--1. Enable the old ChartMuseum repo.
--1. Open the application → **Upgrade**.
--1. Select the chart from the old repo.
--1. Save.
--
--This will reconnect the app to the old repository.
--
--=
--Automated deployments with Jenkins =
--
  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
  == Prerequisites ==

1765548124989-482.59.06.png

Author

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

Size

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

Content

Changes for page Rancher 2

Summary

Details

DevOps-as-a-Service

Navigation