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,16 +315,14 @@
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 a
319	319	{{/info}}
320	320
321	321	(% class="p1" %)
322		-Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chartname>##
	323	+Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chatname>##
323	323
324		-(% class="box" %)
325		-(((
326		-Replace ##<domain>## , ##<project>##  and ##<chartname> ##as necessary to match your set-up. Your charts should be stored in ##<project>-helm ##repository in Harbor, which is created by default when project is created in portal.
327		-)))
	325	+(% class="p1" %)
	326	+Replace ##<domain>## , ##<project>##  and ##<chatname> ##as necessary to match your set-up.
328	328
329	329	(% class="p1" %)
330	330	For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
...	...	@@ -335,116 +335,8 @@
335	335	(% class="wikigeneratedid" %)
336	336	Click Create.
337	337
338		-(% class="wrapped" %)
339		-|=(((
340		-Field
341		-)))|=(((
342		-Value
343		-)))
344		-|=(((
345		-Name
346		-)))|(((
347		-sdcloud-sdportal
348		-)))
349		-|=(((
350		-Description
351		-)))|(((
352		-Sdportal charts of sdcloud project
353		-)))
354		-|=(((
355		-Index URL
356		-)))|(((
357		-oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
	337	+= Automated deployments with Jenkins =
358	358
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.
361		-{{/info}}
362		-)))
363		-
364		-=== Migrating chart repositories in rancher to new OCI Repository format ===
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 two ways to migrate your repositories:
372		-
373		-1. ##Direct Transition (Editing the Existing Repository)##
374		-1*. Change the target to “OCI Repository”.
375		-1*. Update the URL as required (the repository name cannot be changed).
376		-1*. After saving, installed apps will automatically start using the updated repository.
377		-1*. (% class="box" %)
378		-(((
379		-Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
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		-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		-)))
383		-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:
384		-1*. Create a new OCI repository for each chart,
385		-1*. Keep the old ChartMuseum repo enabled during the migration,
386		-1*. Migrate applications gradually following the steps described here.
387		-1*. This avoids disruptions and allows controlled migration.
388		-1. //Special Case: Old Repo Targeting Multiple Chart Repos//
389		-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.
390		-
391		-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
392		-
393		-(% class="box" %)
394		-(((
395		-**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
396		-)))
397		-
398		-| Term | Meaning
399		-| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
400		-| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
401		-
402		-##__**Why This Migration Is Required:**__##
403		-
404		-* ##ChartMuseum is deprecated and will be removed.##
405		-* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
406		-* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
407		-
408		-## Migration Steps:##
409		-
410		-1. ##Create the New OCI Repository in Rancher##
411		-11. Go to **Apps → Repositories**.
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.
414		-11. Point it to the new OCI endpoint.
415		-1. ##Disable the Old ChartMuseum Repository Temporarily##
416		-##This step ensures that Rancher resolves charts from the new OCI repo.##
417		-11. Go to **Apps → Repositories**.
418		-11. Disable the old HTTP(S)-based repository.
419		-11. Keep it disabled until the migration is done.
420		-1. ##Update Existing Applications to Use the New OCI Repo##
421		-Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
422		-11. Go to **Apps → Installed Apps**.
423		-11. Open the application that was deployed using the old repo.
424		-11. Click **Upgrade**.
425		-11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
426		-11. Choose the chart version you want to deploy (same or newer).
427		-11. Click **Upgrade**.
428		-1. ##Re-enable the Old Repository (Optional) ##
429		-If you still need the old repo for other apps, re-enable it after the migration steps above.
430		-**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
431		-
432		-----
433		-
434		-## Reverting the Migration (If Needed)
435		-If you want to move an app back to the old repository:##
436		-
437		-1. Temporarily disable the new OCI repo.
438		-1. Enable the old ChartMuseum repo.
439		-1. Open the application → **Upgrade**.
440		-1. Select the chart from the old repo.
441		-1. Save.
442		-
443		-This will reconnect the app to the old repository.
444		-
445		-=
446		-Automated deployments with Jenkins =
447		-
448	448	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
449	449
450	450	== Prerequisites ==