Changes for page Rancher 2

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • 1765548124989-482.59.06.png
  • 1765548598644-830.png
  • 1765548750604-334.png

Details

Page properties

Content

...	...	@@ -249,9 +249,9 @@
249	249
250	250	oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
251	251
252		-{{info}}
253		-Take into account, that all internal harbor repositories with helm charts have PKEY-helm naming convention, adding repo with both docker images and helm charts may not be supported in rancher.
254		-{{/info}}
	252	+{{box}}
	253	+Take into account, that all internal harbor repositories with helm charts have PKEY-helm naming convention, adding repo with both docker images and helm charts is not supported in rancher.
	254	+{{/box}}
255	255	)))
256	256
257	257	{{info}}
...	...	@@ -287,8 +287,8 @@
287	287	(% class="p1" %)
288	288	Create a new Repository by pressing the Create button.
289	289
290		-(% id="HTarget:http28s29URL-1" class="p1" %)
291		-==== [[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]] ====
	290	+(% class="p1" id="HTarget:http28s29URL-1" %)
	291	+[[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]]
292	292
293	293	(% id="HTarget:http28s29URL-1" class="p1" %)
294	294	==== Target: http(s) URL ====
...	...	@@ -361,7 +361,7 @@
361	361	{{/info}}
362	362	)))
363	363
364		-=== Migrating chart repositories in rancher to new OCI Repository format ===
	364	+== Migrating chart repositories in rancher to new OCI Repository format ==
365	365
366	366	(% class="box warningmessage" %)
367	367	(((
...	...	@@ -368,11 +368,16 @@
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	+(% class="box" %)
	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.**
	374	+)))
	375	+
371	371	There are two ways to migrate your repositories:
372	372
373	373	1. ##Direct Transition (Editing the Existing Repository)##
374	374	1*. Change the target to “OCI Repository”.
375		-1*. Update the URL as required (the repository name cannot be changed).
	380	+1*. Update the URL as required (the repository name cannot be changed), check **Target: OCI Repository** documentation above
376	376	1*. After saving, installed apps will automatically start using the updated repository.
377	377	1*. (% class="box" %)
378	378	(((
...	...	@@ -380,26 +380,17 @@
380	380	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”).
381	381	The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
382	382	)))
383		-1. Add New Repositories One by One (Recommended), prese
384		-This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can:
	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	+
	394	+1. //Special Case: Old Repo Targeting Multiple Chart Repos//
	395	+If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
385	385
386		-* Create a new OCI repository for each chart,
387		-* Keep the old ChartMuseum repo enabled during the migration,
388		-* Migrate applications gradually following the steps described in the main migration guide.
389		-
390		-This avoids disruptions and allows controlled migration.
391		-
392		-Special Case: Old Repo Targeting Multiple Chart Repos
393		-
394		-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.
395		-
396	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	397
398		-(% class="box" %)
399		-(((
400		-**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
401		-)))
402		-
403	403	| Term | Meaning
404	404	| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
405	405	| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
...	...	@@ -415,7 +415,7 @@
415	415	1. ##Create the New OCI Repository in Rancher##
416	416	11. Go to **Apps → Repositories**.
417	417	11. Add a new repository of type **OCI**.
418		-11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
	414	+11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). __**You can't name it the same and can't rename it later.**__
419	419	11. Point it to the new OCI endpoint.
420	420	1. ##Disable the Old ChartMuseum Repository Temporarily##
421	421	##This step ensures that Rancher resolves charts from the new OCI repo.##
...	...	@@ -422,12 +422,15 @@
422	422	11. Go to **Apps → Repositories**.
423	423	11. Disable the old HTTP(S)-based repository.
424	424	11. Keep it disabled until the migration is done.
	421	+[[image:1765548124989-482.59.06.png||height="152" width="485"]]
425	425	1. ##Update Existing Applications to Use the New OCI Repo##
426	426	Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
427	427	11. Go to **Apps → Installed Apps**.
428	428	11. Open the application that was deployed using the old repo.
429		-11. Click **Upgrade**.
430		-11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
	426	+11. Click **Edit/Upgrade**.
	427	+[[image:1765548598644-830.png||height="138" width="811"]]
	428	+11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. Or enter the chart name in search bar:
	429	+[[image:1765548750604-334.png||height="293" width="308"]]
431	431	11. Choose the chart version you want to deploy (same or newer).
432	432	11. Click **Upgrade**.
433	433	1. ##Re-enable the Old Repository (Optional) ##
...	...	@@ -434,9 +434,7 @@
434	434	If you still need the old repo for other apps, re-enable it after the migration steps above.
435	435	**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
436	436
437		-----
438		-
439		-## Reverting the Migration (If Needed)
	436	+##
440	440	If you want to move an app back to the old repository:##
441	441
442	442	1. Temporarily disable the new OCI repo.

1765548124989-482.59.06.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.dianastrebkovat-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+64.4 KB

Content

1765548598644-830.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.dianastrebkovat-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+153.4 KB

Content

1765548750604-334.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.dianastrebkovat-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+103.0 KB

Content