Changes for page Rancher 2

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

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