Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -281,6 +281,7 @@
281	281	(% class="p1" %)
282	282	In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
283	283
	284	+(% class="p1" %)
284	284
285	285	[[image:attach:Screenshot 2023-04-25 at 13.11.48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="400" width="209"]]
286	286
...	...	@@ -315,7 +315,7 @@
315	315	==== Target: OCI Repository ====
316	316
317	317	{{info}}
318		-Now all internal helm charts are stored in harbor folders with -helm suffix. Adding the whole public project doesn't work natively anymore, so each separate chart should be added as a separate repo.//** If you have a real need to add the whole project, please contact support for finding a possible solution.**//
	319	+Now all internal helm charts are stored in harbor folders with -helm suffix. Adding the whole public project doesn't work natively anymore, so each separate chart should be added as a separate repo.//** If you have a real need to add the whole project, please contact support for finding a possible solution.**//
319	319	{{/info}}
320	320
321	321	(% class="p1" %)
...	...	@@ -335,6 +335,7 @@
335	335	(% class="wikigeneratedid" %)
336	336	Click Create.
337	337
	339	+
338	338	(% class="wrapped" %)
339	339	|=(((
340	340	Field
...	...	@@ -344,92 +344,27 @@
344	344	|=(((
345	345	Name
346	346	)))|(((
347		-sdcloud-sdportal
	349	+devopsaas-jenkins-auto-agent
348	348	)))
349	349	|=(((
350	350	Description
351	351	)))|(((
352		-Sdportal charts of sdcloud project
	354	+Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
353	353	)))
354	354	|=(((
355	355	Index URL
356	356	)))|(((
357		-oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
	359	+oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
358	358
	361	+oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
	362	+
359	359	{{info}}
360		-Now we should target a chart repo directly, not the whole project. In you need to reference the whole project with a lot of repos, please contact support to find a possible solution.
	364	+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.
361	361	{{/info}}
362	362	)))
363	363
364		-=== Migrating chart repositories in rancher to new OCI Repository format ===
	368	+= Automated deployments with Jenkins =
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		-)))
370		-
371		-There are 2 ways to "migrate" the repos:
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.
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
377		-
378		-(% class="box" %)
379		-(((
380		-**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
381		-)))
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`).
386		-
387		-##__**Why This Migration Is Required:**__##
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**.##
392		-
393		-## Migration Steps:##
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
416		-
417		-----
418		-
419		-## Reverting the Migration (If Needed)
420		-If you want to move an app back to the old repository:##
421		-
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.
427		-
428		-This will reconnect the app to the old repository.
429		-
430		-=
431		-Automated deployments with Jenkins =
432		-
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 ==