Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -247,7 +247,7 @@
247	247	)))|(((
248	248	oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
249	249
250		-oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-auto-agent
	250	+oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
251	251
252	252	{{box}}
253	253	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.
...	...	@@ -361,7 +361,7 @@
361	361	{{/info}}
362	362	)))
363	363
364		-== Migrating chart repositories in rancher to new OCI Repository format ==
	364	+=== Migrating chart repositories in rancher to new OCI Repository format ===
365	365
366	366	(% class="box warningmessage" %)
367	367	(((
...	...	@@ -377,7 +377,7 @@
377	377
378	378	1. ##Direct Transition (Editing the Existing Repository)##
379	379	1*. Change the target to “OCI Repository”.
380		-1*. Update the URL as required (the repository name cannot be changed), check **Target: OCI Repository** documentation above
	380	+1*. Update the URL as required (the repository name cannot be changed).
381	381	1*. After saving, installed apps will automatically start using the updated repository.
382	382	1*. (% class="box" %)
383	383	(((
...	...	@@ -390,7 +390,6 @@
390	390	1*. Keep the old ChartMuseum repo enabled during the migration,
391	391	1*. Migrate applications gradually following the steps described here.
392	392	1*. This avoids disruptions and allows controlled migration.
393		-
394	394	1. //Special Case: Old Repo Targeting Multiple Chart Repos//
395	395	If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
396	396
...	...	@@ -433,7 +433,8 @@
433	433	If you still need the old repo for other apps, re-enable it after the migration steps above.
434	434	**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
435	435
436		-##If you want to move an app back to the old repository:##
	435	+##
	436	+If you want to move an app back to the old repository:##
437	437
438	438	1. Temporarily disable the new OCI repo.
439	439	1. Enable the old ChartMuseum repo.
...	...	@@ -443,7 +443,8 @@
443	443
444	444	This will reconnect the app to the old repository.
445	445
446		-= Automated deployments with Jenkins =
	446	+=
	447	+Automated deployments with Jenkins =
447	447
448	448	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
449	449