Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -368,12 +368,8 @@
368	368	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)**.
369	369	)))
370	370
371		-There are 2 ways to "migrate" the repos:
	371	+To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
372	372
373		-1.
374		-
375		-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
376		-
377	377	(% class="box" %)
378	378	(((
379	379	**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
...	...	@@ -396,13 +396,12 @@
396	396	11. Add a new repository of type **OCI**.
397	397	11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
398	398	11. Point it to the new OCI endpoint.
399		-1. ##Disable the Old ChartMuseum Repository Temporarily##
400		-##This step ensures that Rancher resolves charts from the new OCI repo.##
	395	+1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.##
401	401	11. Go to **Apps → Repositories**.
402	402	11. Disable the old HTTP(S)-based repository.
403	403	11. Keep it disabled until the migration is done.
404	404	1. ##Update Existing Applications to Use the New OCI Repo##
405		-Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
	400	+##Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.##
406	406	11. Go to **Apps → Installed Apps**.
407	407	11. Open the application that was deployed using the old repo.
408	408	11. Click **Upgrade**.
...	...	@@ -409,9 +409,7 @@
409	409	11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
410	410	11. Choose the chart version you want to deploy (same or newer).
411	411	11. Click **Upgrade**.
412		-1. ##Re-enable the Old Repository (Optional) ##
413		-If you still need the old repo for other apps, re-enable it after the migration steps above.
414		-**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
	407	+1. ##Re-enable the Old Repository (Optional) If you still need the old repo for other apps, re-enable it after the migration steps above.##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
415	415
416	416	----
417	417
...	...	@@ -426,9 +426,24 @@
426	426
427	427	This will reconnect the app to the old repository.
428	428
429		-=
430		-Automated deployments with Jenkins =
	422	+----
431	431
	424	+## Summary
	425	+- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
	426	+- After upgrade, apps no longer track versions from the old repository.
	427	+- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.##
	428	+
	429	+----
	430	+
	431	+If you want, I can also generate:
	432	+- a shorter version (1-pager),
	433	+- a diagram,
	434	+- a Rancher UI screenshot guide,
	435	+- or a version tailored for your team’s internal wiki.
	436	+
	437	+
	438	+= Automated deployments with Jenkins =
	439	+
432	432	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
433	433
434	434	== Prerequisites ==