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
...	...	@@ -316,7 +316,7 @@
316	316	==== Target: OCI Repository ====
317	317
318	318	{{info}}
319		-Now all internal helm charts are stored in harbor folders with -helm suffix. Adding the whole public project doesn't work natively anymore, so each separate chart should be added as a separate repo.//** If you have a real need to add the whole project, please contact support for finding a possible solution.**//
	318	+Now all internal helm charts are stored in harbor folders with -helm suffix. Adding the whole public project doesn't work natively anymore, so each separate chart should be added as a separate repo.//** If you have a real need to add the whole project, please contact support for finding a possible solution.**//
320	320	{{/info}}
321	321
322	322	(% class="p1" %)
...	...	@@ -336,7 +336,6 @@
336	336	(% class="wikigeneratedid" %)
337	337	Click Create.
338	338
339		-
340	340	(% class="wrapped" %)
341	341	|=(((
342	342	Field
...	...	@@ -346,25 +346,97 @@
346	346	|=(((
347	347	Name
348	348	)))|(((
349		-devopsaas-jenkins-auto-agent
	347	+sdcloud-sdportal
350	350	)))
351	351	|=(((
352	352	Description
353	353	)))|(((
354		-Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
	352	+Sdportal charts of sdcloud project
355	355	)))
356	356	|=(((
357	357	Index URL
358	358	)))|(((
359		-oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
	357	+oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
360	360
361		-oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
362		-
363	363	{{info}}
364		-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.
	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.
365	365	{{/info}}
366	366	)))
367	367
	364	+=== Migrating chart repositories in rancher to new OCI Repository format ===
	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	+To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
	372	+
	373	+(% class="box" %)
	374	+(((
	375	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
	376	+)))
	377	+
	378	+| Term | Meaning
	379	+| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
	380	+| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
	381	+
	382	+##__**Why This Migration Is Required:**__##
	383	+
	384	+* ##ChartMuseum is deprecated and will be removed.##
	385	+* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
	386	+* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
	387	+
	388	+## Migration Steps:##
	389	+
	390	+1. ##Create the New OCI Repository in Rancher##
	391	+11. Go to **Apps → Repositories**.
	392	+11. Add a new repository of type **OCI**.
	393	+11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
	394	+11. Point it to the new OCI endpoint.
	395	+1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.##
	396	+11. Go to **Apps → Repositories**.
	397	+11. Disable the old HTTP(S)-based repository.
	398	+11. Keep it disabled until the migration is done.
	399	+1. ##Update Existing Applications to Use the New OCI Repo##
	400	+##Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.##
	401	+11. Go to **Apps → Installed Apps**.
	402	+11. Open the application that was deployed using the old repo.
	403	+11. Click **Upgrade**.
	404	+11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
	405	+11. Choose the chart version you want to deploy (same or newer).
	406	+11. Click **Upgrade**.
	407	+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
	408	+
	409	+----
	410	+
	411	+## Reverting the Migration (If Needed)
	412	+If you want to move an app back to the old repository:##
	413	+
	414	+1. Temporarily disable the new OCI repo.
	415	+1. Enable the old ChartMuseum repo.
	416	+1. Open the application → **Upgrade**.
	417	+1. Select the chart from the old repo.
	418	+1. Save.
	419	+
	420	+This will reconnect the app to the old repository.
	421	+
	422	+----
	423	+
	424	+## Summary
	425	+- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
	426	+- After upgrade, apps no longer track versions from the old repository.
	427	+- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.##
	428	+
	429	+----
	430	+
	431	+If you want, I can also generate:
	432	+- a shorter version (1-pager),
	433	+- a diagram,
	434	+- a Rancher UI screenshot guide,
	435	+- or a version tailored for your team’s internal wiki.
	436	+
	437	+
368	368	= Automated deployments with Jenkins =
369	369
370	370	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.