Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -368,38 +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 two ways to migrate your repositories:
	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. ##Direct Transition (Editing the Existing Repository)##
374		-11. Change the target to “OCI Repository”.
375		-11. Update the URL as required (the repository name cannot be changed).
376		-
377		-1. Direct Transition (Editing the Existing Repository).You can modify the existing repository directly:
378		-Change the target to “OCI Repository”.Update the URL as required (the repository name cannot be changed).
379		-
380		-After saving, installed apps will automatically start using the updated repository.
381		-
382		-Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
383		-If your old repository included several charts (for example “bitbucket” and “jira”), then after switching to OCI you can only target one chart (e.g. “bitbucket”).
384		-The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
385		-
386		-1. Add New Repositories One by One (Recommended)
387		-
388		-This approach allows a smooth transition while the old ChartMuseum repository continues to function.
389		-You can:
390		-
391		-* Create a new OCI repository for each chart,
392		-* Keep the old ChartMuseum repo enabled during the migration,
393		-* Migrate applications gradually following the steps described in the main migration guide.
394		-
395		-This avoids disruptions and allows controlled migration.
396		-
397		-Special Case: Old Repo Targeting Multiple Chart Repos
398		-
399		-If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please contact support. OCI does not support multi-chart endpoints within a single repository, and we can help you find an appropriate solution.
400		-
401		-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
402		-
403	403	(% class="box" %)
404	404	(((
405	405	**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
...	...	@@ -422,13 +422,12 @@
422	422	11. Add a new repository of type **OCI**.
423	423	11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
424	424	11. Point it to the new OCI endpoint.
425		-1. ##Disable the Old ChartMuseum Repository Temporarily##
426		-##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.##
427	427	11. Go to **Apps → Repositories**.
428	428	11. Disable the old HTTP(S)-based repository.
429	429	11. Keep it disabled until the migration is done.
430	430	1. ##Update Existing Applications to Use the New OCI Repo##
431		-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.##
432	432	11. Go to **Apps → Installed Apps**.
433	433	11. Open the application that was deployed using the old repo.
434	434	11. Click **Upgrade**.
...	...	@@ -435,26 +435,41 @@
435	435	11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
436	436	11. Choose the chart version you want to deploy (same or newer).
437	437	11. Click **Upgrade**.
438		-1. ##Re-enable the Old Repository (Optional) ##
439		-If you still need the old repo for other apps, re-enable it after the migration steps above.
440		-**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.##
441	441
442		-----
	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.
443	443
	411	+-----
	412	+
444	444	## Reverting the Migration (If Needed)
445	445	If you want to move an app back to the old repository:##
446	446
447	447	1. Temporarily disable the new OCI repo.
448		-1. Enable the old ChartMuseum repo.
449		-1. Open the application → **Upgrade**.
450		-1. Select the chart from the old repo.
451		-1. Save.
	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.
452	452
453	453	This will reconnect the app to the old repository.
454	454
455		-=
456		-Automated deployments with Jenkins =
	424	+-----
457	457
	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	+
458	458	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
459	459
460	460	== Prerequisites ==