Changes for page Rancher 2

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 3 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		-{{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}}
	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}}
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		-(% 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"]]
	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"]] ====
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,33 +368,18 @@
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		-)))
	371	+There are 2 ways to "migrate" the repos:
375	375
376		-There are two ways to migrate your repositories:
	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.
377	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" %)
	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
	377	+
	378	+(% class="box" %)
383	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.
	380	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
387	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	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`).
...	...	@@ -410,7 +410,7 @@
410	410	1. ##Create the New OCI Repository in Rancher##
411	411	11. Go to **Apps → Repositories**.
412	412	11. Add a new repository of type **OCI**.
413		-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.**__
	398	+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	415	1. ##Disable the Old ChartMuseum Repository Temporarily##
416	416	##This step ensures that Rancher resolves charts from the new OCI repo.##
...	...	@@ -417,15 +417,12 @@
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		-[[image:1765548124989-482.59.06.png||height="152" width="485"]]
421	421	1. ##Update Existing Applications to Use the New OCI Repo##
422	422	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		-11. Click **Edit/Upgrade**.
426		-[[image:1765548598644-830.png||height="138" width="811"]]
427		-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:
428		-[[image:1765548750604-334.png||height="293" width="308"]]
	409	+11. Click **Upgrade**.
	410	+11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
429	429	11. Choose the chart version you want to deploy (same or newer).
430	430	11. Click **Upgrade**.
431	431	1. ##Re-enable the Old Repository (Optional) ##
...	...	@@ -432,7 +432,9 @@
432	432	If you still need the old repo for other apps, re-enable it after the migration steps above.
433	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	434
435		-##
	417	+----
	418	+
	419	+## Reverting the Migration (If Needed)
436	436	If you want to move an app back to the old repository:##
437	437
438	438	1. Temporarily disable the new OCI repo.

1765548124989-482.59.06.png

Author

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

Size

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

Content

1765548598644-830.png

Author

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

Size

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

Content

1765548750604-334.png

Author

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

Size

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

Content