Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -368,8 +368,12 @@
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		-To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
	371	+There are 2 ways to "migrate" the repos:
372	372
	373	+1. You can do the fast transition - edit already existing repository – choose //Target: OCI repository //and adapt the url (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The problem is that the OCI repository recommends to target chart repos in the url, not the whole folder anymore.  That means if you deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket"
	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	+
373	373	(% class="box" %)
374	374	(((
375	375	**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
...	...	@@ -392,12 +392,13 @@
392	392	11. Add a new repository of type **OCI**.
393	393	11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
394	394	11. Point it to the new OCI endpoint.
395		-1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.##
	399	+1. ##Disable the Old ChartMuseum Repository Temporarily##
	400	+##This step ensures that Rancher resolves charts from the new OCI repo.##
396	396	11. Go to **Apps → Repositories**.
397	397	11. Disable the old HTTP(S)-based repository.
398	398	11. Keep it disabled until the migration is done.
399	399	1. ##Update Existing Applications to Use the New OCI Repo##
400		-##Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.##
	405	+Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
401	401	11. Go to **Apps → Installed Apps**.
402	402	11. Open the application that was deployed using the old repo.
403	403	11. Click **Upgrade**.
...	...	@@ -404,41 +404,26 @@
404	404	11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
405	405	11. Choose the chart version you want to deploy (same or newer).
406	406	11. Click **Upgrade**.
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.##
	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
408	408
409		- 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.
	416	+----
410	410
411		------
412		-
413	413	## Reverting the Migration (If Needed)
414	414	If you want to move an app back to the old repository:##
415	415
416	416	1. Temporarily disable the new OCI repo.
417		-2. Enable the old ChartMuseum repo.
418		-3. Open the application → **Upgrade**.
419		-4. Select the chart from the old repo.
420		-5. Save.
	422	+1. Enable the old ChartMuseum repo.
	423	+1. Open the application → **Upgrade**.
	424	+1. Select the chart from the old repo.
	425	+1. Save.
421	421
422	422	This will reconnect the app to the old repository.
423	423
424		------
	429	+=
	430	+Automated deployments with Jenkins =
425	425
426		-## Summary
427		-- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
428		-- After upgrade, apps no longer track versions from the old repository.
429		-- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.##
430		-
431		------
432		-
433		-If you want, I can also generate:
434		-- a shorter version (1-pager),
435		-- a diagram,
436		-- a Rancher UI screenshot guide,
437		-- or a version tailored for your team’s internal wiki.
438		-
439		-
440		-= Automated deployments with Jenkins =
441		-
442	442	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
443	443
444	444	== Prerequisites ==