Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -368,33 +368,13 @@
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.
	372	+
371	371	(% class="box" %)
372	372	(((
373		-**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.**
	375	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
374	374	)))
375	375
376		-There are two ways to migrate your repositories:
377		-
378		-1. ##Direct Transition (Editing the Existing Repository)##
379		-1*. Change the target to “OCI Repository”.
380		-1*. Update the URL as required (the repository name cannot be changed).
381		-1*. After saving, installed apps will automatically start using the updated repository.
382		-1*. (% class="box" %)
383		-(((
384		-Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
385		-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”).
386		-The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
387		-)))
388		-1. Add New Repositories One by One (Recommended), preserve the old one till the end. This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can:
389		-1*. Create a new OCI repository for each chart,
390		-1*. Keep the old ChartMuseum repo enabled during the migration,
391		-1*. Migrate applications gradually following the steps described here.
392		-1*. This avoids disruptions and allows controlled migration.
393		-1. //Special Case: Old Repo Targeting Multiple Chart Repos//
394		-If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
395		-
396		-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
397		-
398	398	| Term | Meaning
399	399	| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
400	400	| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
...	...	@@ -412,14 +412,12 @@
412	412	11. Add a new repository of type **OCI**.
413	413	11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
414	414	11. Point it to the new OCI endpoint.
415		-1. ##Disable the Old ChartMuseum Repository Temporarily##
416		-##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.##
417	417	11. Go to **Apps → Repositories**.
418	418	11. Disable the old HTTP(S)-based repository.
419	419	11. Keep it disabled until the migration is done.
420		-
421	421	1. ##Update Existing Applications to Use the New OCI Repo##
422		-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.##
423	423	11. Go to **Apps → Installed Apps**.
424	424	11. Open the application that was deployed using the old repo.
425	425	11. Click **Upgrade**.
...	...	@@ -426,9 +426,7 @@
426	426	11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
427	427	11. Choose the chart version you want to deploy (same or newer).
428	428	11. Click **Upgrade**.
429		-1. ##Re-enable the Old Repository (Optional) ##
430		-If you still need the old repo for other apps, re-enable it after the migration steps above.
431		-**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
432	432
433	433	----
434	434
...	...	@@ -443,9 +443,24 @@
443	443
444	444	This will reconnect the app to the old repository.
445	445
446		-=
447		-Automated deployments with Jenkins =
	422	+----
448	448
	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	+
449	449	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
450	450
451	451	== Prerequisites ==