Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -335,7 +335,6 @@
335	335	(% class="wikigeneratedid" %)
336	336	Click Create.
337	337
338		-
339	339	(% class="wrapped" %)
340	340	|=(((
341	341	Field
...	...	@@ -364,105 +364,98 @@
364	364
365	365	=== Migrating chart repositories in rancher to new OCI Repository format ===
366	366
367		-(% class="wikigeneratedid" %)
	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	+)))
368	368
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)**.##
	371	+There are two ways to migrate your repositories:
370	370
371		-To ensure a smooth transition, we recomment should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
	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).
372	372
373		-We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.
	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).
374	374
375		------
	380	+After saving, installed apps will automatically start using the updated repository.
376	376
377		-## Terminology##
	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.
378	378
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`). |
	386	+1. Add New Repositories One by One (Recommended)
383	383
384		------
	388	+This approach allows a smooth transition while the old ChartMuseum repository continues to function.
	389	+You can:
385	385
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**.##
	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.
390	390
391		------
	395	+This avoids disruptions and allows controlled migration.
392	392
393		-## Migration Steps##
	397	+Special Case: Old Repo Targeting Multiple Chart Repos
394	394
395		-### 1. Create the New OCI Repository in Rancher##
	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.
396	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	+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
401	401
402		------
	403	+(% class="box" %)
	404	+(((
	405	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
	406	+)))
403	403
404		-### 2. Disable the Old ChartMuseum Repository Temporarily
405		-This step ensures that Rancher resolves charts from the new OCI repo.##
	408	+| Term | Meaning
	409	+| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
	410	+| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
406	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.
	412	+##__**Why This Migration Is Required:**__##
410	410
411		------
	414	+* ##ChartMuseum is deprecated and will be removed.##
	415	+* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
	416	+* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
412	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.##
	418	+## Migration Steps:##
416	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**.
	420	+1. ##Create the New OCI Repository in Rancher##
	421	+11. Go to **Apps → Repositories**.
	422	+11. Add a new repository of type **OCI**.
	423	+11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
	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.##
	427	+11. Go to **Apps → Repositories**.
	428	+11. Disable the old HTTP(S)-based repository.
	429	+11. Keep it disabled until the migration is done.
	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.
	432	+11. Go to **Apps → Installed Apps**.
	433	+11. Open the application that was deployed using the old repo.
	434	+11. Click **Upgrade**.
	435	+11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
	436	+11. Choose the chart version you want to deploy (same or newer).
	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
423	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.
	442	+----
427	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		-
437	437	## Reverting the Migration (If Needed)
438	438	If you want to move an app back to the old repository:##
439	439
440	440	1. Temporarily disable the new OCI repo.
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.
	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.
445	445
446	446	This will reconnect the app to the old repository.
447	447
448		------
	455	+=
	456	+Automated deployments with Jenkins =
449	449
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		-
466	466	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
467	467
468	468	== Prerequisites ==