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 Helm Chart
	232	+* Read Artifact
233	233	* Pull Repository
234	234
235	235	(% id="HCreateAppRepositoryinRancher-1" class="p1" %)
...	...	@@ -238,7 +238,6 @@
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		-
242	242	[[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"]]
243	243
244	244	(% class="p1" %)
...	...	@@ -248,29 +248,8 @@
248	248	[[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"]]
249	249
250	250	(% id="HTarget:http28s29URL-1" class="p1" %)
251		-==== Target: http(s) URL ====
	250	+==== ====
252	252
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		-
274	274	{{info}}
275	275	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.**//
276	276	{{/info}}
...	...	@@ -322,12 +322,12 @@
322	322
323	323	(% class="box warningmessage" %)
324	324	(((
325		-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)**.
	303	+ChartMuseum is deprecated. **All harbor charts are removed from ChartMuseum**, and **old HTTP(S)-based chart repositories no longer work in Rancher (for internal harbor charts)**.
326	326	)))
327	327
328	328	(% class="box" %)
329	329	(((
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.**
	308	+**All your charts are available in the corresponding  `<pkey>-helm` OCI project.**
331	331	)))
332	332
333	333	There are two ways to migrate your repositories:
...	...	@@ -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
	315	+1*. Update the URL as required (the repository name cannot be changed) and add a new robot account for helm project, check documentation above
338	338	1*. After saving, installed apps will automatically start using the updated repository.
339	339	1*. (% class="box" %)
340	340	(((
...	...	@@ -351,8 +351,6 @@
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
354		-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
355		-
356	356	| Term | Meaning
357	357	| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
358	358	| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
...	...	@@ -359,7 +359,7 @@
359	359
360	360	##__**Why This Migration Is Required:**__##
361	361
362		-* ##ChartMuseum is deprecated and will be removed.##
	338	+* ##ChartMuseum is deprecated.##
363	363	* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
364	364	* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
365	365