Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -177,6 +177,49 @@
177	177	(% class="p1" %)
178	178	[[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]]
179	179
	180	+(% id="H" class="p1" %)
	181	+==== Target: http(s) URL ====
	182	+
	183	+{{warning}}
	184	+This example is being deprecated, you can still add other external repositories in that way, but all internal harbor-hosted repositories should be added as Target: OCI Repository
	185	+{{/warning}}
	186	+
	187	+(% class="p1" %)
	188	+In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
	189	+
	190	+(% class="wrapped" %)
	191	+|=(((
	192	+Field
	193	+)))|=(((
	194	+Value
	195	+)))
	196	+|=(((
	197	+Name
	198	+)))|(((
	199	+devops-as-a-service
	200	+)))
	201	+|=(((
	202	+Description
	203	+)))|(((
	204	+Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
	205	+)))
	206	+|=(((
	207	+Index URL
	208	+)))|(((
	209	+[[https:~~/~~/registry.sdc.t-systems.net/chartrepo/devopsaas/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]]
	210	+)))
	211	+
	212	+[[image:attach:image-2024-2-27_14-29-17.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="540"]]
	213	+
	214	+(% class="p1" %)
	215	+Finally, click Create.
	216	+
	217	+The repository is now listed:
	218	+
	219	+[[image:Screenshot 2024-07-03 at 15.13.55.png||data-xwiki-image-style-border="true" height="149" width="785"]]
	220	+
	221	+==== Target: OCI Repository ====
	222	+
180	180	To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
181	181
182	182	[[image:1765207154466-828.png||height="298" width="821"]]
...	...	@@ -204,7 +204,7 @@
204	204	)))|(((
205	205	oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
206	206
207		-oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-auto-agent
	250	+oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
208	208
209	209	{{box}}
210	210	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.
...	...	@@ -334,7 +334,7 @@
334	334
335	335	1. ##Direct Transition (Editing the Existing Repository)##
336	336	1*. Change the target to “OCI Repository”.
337		-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).
338	338	1*. After saving, installed apps will automatically start using the updated repository.
339	339	1*. (% class="box" %)
340	340	(((
...	...	@@ -347,7 +347,6 @@
347	347	1*. Keep the old ChartMuseum repo enabled during the migration,
348	348	1*. Migrate applications gradually following the steps described here.
349	349	1*. This avoids disruptions and allows controlled migration.
350		-
351	351	1. //Special Case: Old Repo Targeting Multiple Chart Repos//
352	352	If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
353	353
...	...	@@ -390,7 +390,8 @@
390	390	If you still need the old repo for other apps, re-enable it after the migration steps above.
391	391	**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
392	392
393		-##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:##
394	394
395	395	1. Temporarily disable the new OCI repo.
396	396	1. Enable the old ChartMuseum repo.
...	...	@@ -400,7 +400,8 @@
400	400
401	401	This will reconnect the app to the old repository.
402	402
403		-= Automated deployments with Jenkins =
	446	+=
	447	+Automated deployments with Jenkins =
404	404
405	405	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
406	406