Changes for page Rancher 2

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
...	...	@@ -356,7 +356,7 @@
356	356	|=(((
357	357	Index URL
358	358	)))|(((
359		-oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal,
	357	+oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
360	360
361	361	{{info}}
362	362	Now we should target a chart repo directly, not the whole project. In you need to reference the whole project with a lot of repos, please contact support to find a possible solution.
...	...	@@ -363,8 +363,95 @@
363	363	{{/info}}
364	364	)))
365	365
366		-= Automated deployments with Jenkins =
	364	+=== Migrating chart repositories in rancher to new OCI Repository format ===
367	367
	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	+)))
	370	+
	371	+(% class="box" %)
	372	+(((
	373	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. After m**
	374	+)))
	375	+
	376	+There are two ways to migrate your repositories:
	377	+
	378	+1. ##Direct Transition (Editing the Existing Repository)##
	379	+1*. Change the target to “OCI Repository”.
	380	+1*. Update the URL as required (the repository name cannot be changed).
	381	+1*. After saving, installed apps will automatically start using the updated repository.
	382	+1*. (% class="box" %)
	383	+(((
	384	+Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
	385	+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”).
	386	+The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
	387	+)))
	388	+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:
	389	+1*. Create a new OCI repository for each chart,
	390	+1*. Keep the old ChartMuseum repo enabled during the migration,
	391	+1*. Migrate applications gradually following the steps described here.
	392	+1*. This avoids disruptions and allows controlled migration.
	393	+1. //Special Case: Old Repo Targeting Multiple Chart Repos//
	394	+If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
	395	+
	396	+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
	397	+
	398	+(% class="box" %)
	399	+(((
	400	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
	401	+)))
	402	+
	403	+| Term | Meaning
	404	+| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
	405	+| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
	406	+
	407	+##__**Why This Migration Is Required:**__##
	408	+
	409	+* ##ChartMuseum is deprecated and will be removed.##
	410	+* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
	411	+* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
	412	+
	413	+## Migration Steps:##
	414	+
	415	+1. ##Create the New OCI Repository in Rancher##
	416	+11. Go to **Apps → Repositories**.
	417	+11. Add a new repository of type **OCI**.
	418	+11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
	419	+11. Point it to the new OCI endpoint.
	420	+1. ##Disable the Old ChartMuseum Repository Temporarily##
	421	+##This step ensures that Rancher resolves charts from the new OCI repo.##
	422	+11. Go to **Apps → Repositories**.
	423	+11. Disable the old HTTP(S)-based repository.
	424	+11. Keep it disabled until the migration is done.
	425	+1. ##Update Existing Applications to Use the New OCI Repo##
	426	+Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
	427	+11. Go to **Apps → Installed Apps**.
	428	+11. Open the application that was deployed using the old repo.
	429	+11. Click **Upgrade**.
	430	+11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
	431	+11. Choose the chart version you want to deploy (same or newer).
	432	+11. Click **Upgrade**.
	433	+1. ##Re-enable the Old Repository (Optional) ##
	434	+If you still need the old repo for other apps, re-enable it after the migration steps above.
	435	+**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
	436	+
	437	+----
	438	+
	439	+## Reverting the Migration (If Needed)
	440	+If you want to move an app back to the old repository:##
	441	+
	442	+1. Temporarily disable the new OCI repo.
	443	+1. Enable the old ChartMuseum repo.
	444	+1. Open the application → **Upgrade**.
	445	+1. Select the chart from the old repo.
	446	+1. Save.
	447	+
	448	+This will reconnect the app to the old repository.
	449	+
	450	+=
	451	+Automated deployments with Jenkins =
	452	+
368	368	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
369	369
370	370	== Prerequisites ==