Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -229,7 +229,7 @@
229	229
230	230	To add project specific helm charts to Rancher, a Harbor robot account is needed, that is able to read helm charts and pull repositories. If you don't have such an account yet, please follow the instructions given in the [[Create Robot Account section of the Harbor documentation>>doc:Harbor.Harbor 2\.7 Robot Accounts.WebHome||anchor="create_robot_account"]] and make sure to grant at least the following permissions:
231	231
232		-* Read Artifact
	232	+* Read Helm Chart
233	233	* Pull Repository
234	234
235	235	(% id="HCreateAppRepositoryinRancher-1" class="p1" %)
...	...	@@ -238,6 +238,7 @@
238	238	(% class="p1" %)
239	239	In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
240	240
	241	+
241	241	[[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"]]
242	242
243	243	(% class="p1" %)
...	...	@@ -247,8 +247,29 @@
247	247	[[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"]]
248	248
249	249	(% id="HTarget:http28s29URL-1" class="p1" %)
250		-==== ====
	251	+==== Target: http(s) URL ====
251	251
	253	+{{warning title="Chartmuseum Deprecation"}}
	254	+Chartmuseum in Harbor is deprecated, meaning we won't be able to add internal harbor repositories to Rancher that way anymore. Instead use Target: OCI repository.
	255	+{{/warning}}
	256	+
	257	+(% class="p1" %)
	258	+A name for the Repository has to be set. In the screenshot, the project name CITEST is used, which corresponds to our example from above.
	259	+Choose http(s) URL to an index generated by Helm and provide the Index URL ##https:~/~/registry-<domain>.devops.t-systems.net/chartrepo/<project>/##
	260	+
	261	+(% class="p1" %)
	262	+Replace ##<domain>## and ##<project>## as necessary to match your set-up.
	263	+
	264	+(% class="p1" %)
	265	+For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
	266	+[[image:attach:Screenshot 2023-04-26 at 18.10.15.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="468" width="1100"]]
	267	+
	268	+(% class="p1" %)
	269	+Click Create.
	270	+
	271	+(% id="HTarget:OCIRepository-1" class="p1" %)
	272	+==== Target: OCI Repository ====
	273	+
252	252	{{info}}
253	253	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.**//
254	254	{{/info}}
...	...	@@ -305,7 +305,7 @@
305	305
306	306	(% class="box" %)
307	307	(((
308		-**All your charts are available in the corresponding  `<pkey>-helm` OCI project.**
	330	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. During migration, please adapt your helm push commands and url's for new oci-compatible repository.**
309	309	)))
310	310
311	311	There are two ways to migrate your repositories:
...	...	@@ -312,7 +312,7 @@
312	312
313	313	1. ##Direct Transition (Editing the Existing Repository)##
314	314	1*. Change the target to “OCI Repository”.
315		-1*. Update the URL as required (the repository name cannot be changed) and add a new robot account for hel, check documentation above
	337	+1*. Update the URL as required (the repository name cannot be changed), check **Target: OCI Repository** documentation above
316	316	1*. After saving, installed apps will automatically start using the updated repository.
317	317	1*. (% class="box" %)
318	318	(((