Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -158,10 +158,6 @@
158	158
159	159	== Add public helm chart ==
160	160
161		-{{warning width="70" title="Chartmuseum Deprecation"}}
162		-Chartmuseum is deprecated in new Harbor versions, we are migrating all helm charts to oci-compatible repositories in Harbor with "PKEY-helm" naming convention. For internal harbor repos, use new approach to add OCI chart repositories in rancher.
163		-{{/warning}}
164		-
165	165	In this section, we describe (% style="color:#172b4d" %)how to add public helm charts like the one of DevOps-as-a-Service to a cluster to allow manual deployments.
166	166
167	167	(% id="HCreateAppRepositoryinRancher" class="p1" %)
...	...	@@ -300,7 +300,7 @@
300	300
301	301	(% class="box warningmessage" %)
302	302	(((
303		-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)**.
	299	+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)**.
304	304	)))
305	305
306	306	(% class="box" %)
...	...	@@ -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
	311	+1*. Update the URL as required (the repository name cannot be changed) and add a new robot account for helm project, check documentation above
316	316	1*. After saving, installed apps will automatically start using the updated repository.
317	317	1*. (% class="box" %)
318	318	(((
...	...	@@ -329,8 +329,6 @@
329	329	1. //Special Case: Old Repo Targeting Multiple Chart Repos//
330	330	If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
331	331
332		-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
333		-
334	334	| Term | Meaning
335	335	| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
336	336	| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
...	...	@@ -337,7 +337,7 @@
337	337
338	338	##__**Why This Migration Is Required:**__##
339	339
340		-* ##ChartMuseum is deprecated and will be removed.##
	334	+* ##ChartMuseum is deprecated.##
341	341	* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
342	342	* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
343	343