Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -335,6 +335,7 @@
335	335	(% class="wikigeneratedid" %)
336	336	Click Create.
337	337
	338	+
338	338	(% class="wrapped" %)
339	339	|=(((
340	340	Field
...	...	@@ -363,73 +363,105 @@
363	363
364	364	=== Migrating chart repositories in rancher to new OCI Repository format ===
365	365
366		-(% class="box warningmessage" %)
367		-(((
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		-)))
	367	+(% class="wikigeneratedid" %)
370	370
371		-There are 2 ways to "migrate" the repos:
	369	+##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)**.##
372	372
373		-1. You can do t transition  and edit already existing repository – choose //Target: OCI repository, //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", you will still need to create a new repo targeting "jira".
374		-1.
	371	+To ensure a smooth transition, we recomment should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
375	375
376		-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
	373	+We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.
377	377
378		-(% class="box" %)
379		-(((
380		-**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
381		-)))
	375	+-----
382	382
383		-| Term | Meaning
384		-| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
385		-| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
	377	+## Terminology##
386	386
387		-##__**Why This Migration Is Required:**__##
	379	+| Term | Meaning |
	380	+| |-|
	381	+| **Old Repository** | The existing HTTP/HTTPS ChartMuseum repository. |
	382	+| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). |
388	388
389		-* ##ChartMuseum is deprecated and will be removed.##
390		-* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
391		-* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
	384	+-----
392	392
393		-## Migration Steps:##
	386	+## Why This Migration Is Required
	387	+- ChartMuseum is deprecated and will be removed.
	388	+- Applications deployed from old repos keep a reference to that repo inside their labels.
	389	+- Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions**.##
394	394
395		-1. ##Create the New OCI Repository in Rancher##
396		-11. Go to **Apps → Repositories**.
397		-11. Add a new repository of type **OCI**.
398		-11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
399		-11. Point it to the new OCI endpoint.
400		-1. ##Disable the Old ChartMuseum Repository Temporarily##
401		-##This step ensures that Rancher resolves charts from the new OCI repo.##
402		-11. Go to **Apps → Repositories**.
403		-11. Disable the old HTTP(S)-based repository.
404		-11. Keep it disabled until the migration is done.
405		-1. ##Update Existing Applications to Use the New OCI Repo##
406		-Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
407		-11. Go to **Apps → Installed Apps**.
408		-11. Open the application that was deployed using the old repo.
409		-11. Click **Upgrade**.
410		-11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
411		-11. Choose the chart version you want to deploy (same or newer).
412		-11. Click **Upgrade**.
413		-1. ##Re-enable the Old Repository (Optional) ##
414		-If you still need the old repo for other apps, re-enable it after the migration steps above.
415		-**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
	391	+-----
416	416
417		-----
	393	+## Migration Steps##
418	418
	395	+### 1. Create the New OCI Repository in Rancher##
	396	+
	397	+1. Go to **Apps → Repositories**.
	398	+2. Add a new repository of type **OCI**.
	399	+3. Name it exactly like your old repo name (e.g. `<chart-repo-name>`).
	400	+4. Point it to the new OCI endpoint.
	401	+
	402	+-----
	403	+
	404	+### 2. Disable the Old ChartMuseum Repository Temporarily
	405	+This step ensures that Rancher resolves charts from the new OCI repo.##
	406	+
	407	+1. Go to **Apps → Repositories**.
	408	+2. Disable the old HTTP(S)-based repository.
	409	+3. Keep it disabled until the migration is done.
	410	+
	411	+-----
	412	+
	413	+### 3. Update Existing Applications to Use the New OCI Repo
	414	+Applications deployed with the old repository still contain the old repo name in their metadata.
	415	+You must upgrade them once to transition.##
	416	+
	417	+1. Go to **Apps → Installed Apps**.
	418	+2. Open the application that was deployed using the old repo.
	419	+3. Click **Upgrade**.
	420	+4. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
	421	+5. Choose the chart version you want to deploy (same or newer).
	422	+6. Click **Upgrade**.
	423	+
	424	+After this upgrade:
	425	+- Your application is now linked to the **new OCI repository**.
	426	+- Rancher will show upgrade notifications only for versions available in the new repo.
	427	+
	428	+-----
	429	+
	430	+### 4. Re-enable the Old Repository (Optional)
	431	+If you still need the old repo for other apps, re-enable it after the migration steps above.##
	432	+
	433	+> 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.
	434	+
	435	+-----
	436	+
419	419	## Reverting the Migration (If Needed)
420	420	If you want to move an app back to the old repository:##
421	421
422	422	1. Temporarily disable the new OCI repo.
423		-1. Enable the old ChartMuseum repo.
424		-1. Open the application → **Upgrade**.
425		-1. Select the chart from the old repo.
426		-1. Save.
	441	+2. Enable the old ChartMuseum repo.
	442	+3. Open the application → **Upgrade**.
	443	+4. Select the chart from the old repo.
	444	+5. Save.
427	427
428	428	This will reconnect the app to the old repository.
429	429
430		-=
431		-Automated deployments with Jenkins =
	448	+-----
432	432
	450	+## Summary
	451	+- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
	452	+- After upgrade, apps no longer track versions from the old repository.
	453	+- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.##
	454	+
	455	+-----
	456	+
	457	+If you want, I can also generate:
	458	+- a shorter version (1-pager),
	459	+- a diagram,
	460	+- a Rancher UI screenshot guide,
	461	+- or a version tailored for your team’s internal wiki.
	462	+
	463	+
	464	+= Automated deployments with Jenkins =
	465	+
433	433	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
434	434
435	435	== Prerequisites ==