Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -255,7 +255,7 @@
255	255	)))
256	256
257	257	{{info}}
258		-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 need in adding the w
	258	+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 need in adding the whole project with many repositories, please contact support for finding a possible solution.**//
259	259	{{/info}}
260	260
261	261	=== Deploy Helm charts ===
...	...	@@ -268,7 +268,6 @@
268	268
269	269	== Add private chart repository ==
270	270
271		-
272	272	=== Create a robot account in Harbor ===
273	273
274	274	To add project specific helm charts to Rancher, a Harbor robot account is needed, that is able to read helm charts and pull repositories. If you don't have such an account yet, please follow the instructions given in the [[Create Robot Account section of the Harbor documentation>>doc:Harbor.Harbor 2\.7 Robot Accounts.WebHome||anchor="create_robot_account"]] and make sure to grant at least the following permissions:
...	...	@@ -281,6 +281,8 @@
281	281
282	282	(% class="p1" %)
283	283	In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
	283	+
	284	+
284	284	[[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"]]
285	285
286	286	(% class="p1" %)
...	...	@@ -293,7 +293,7 @@
293	293	==== Target: http(s) URL ====
294	294
295	295	{{warning title="Chartmuseum Deprecation"}}
296		-Chartmuseum in Harbor is deprecated, meaning we won't be able to add repositories to Rancher that way anymore. Instead use Target: OCI repository.
	297	+Chartmuseum in Harbor is deprecated, meaning we won't be able to add internal harbor repositories to Rancher that way anymore. Instead use Target: OCI repository.
297	297	{{/warning}}
298	298
299	299	(% class="p1" %)
...	...	@@ -314,14 +314,16 @@
314	314	==== Target: OCI Repository ====
315	315
316	316	{{info}}
317		-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.
	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.**//
318	318	{{/info}}
319	319
320	320	(% class="p1" %)
321		-Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chatname>##
	322	+Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chartname>##
322	322
323		-(% class="p1" %)
324		-Replace ##<domain>## , ##<project>##  and ##<chatname> ##as necessary to match your set-up.
	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	325
326	326	(% class="p1" %)
327	327	For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
...	...	@@ -332,8 +332,102 @@
332	332	(% class="wikigeneratedid" %)
333	333	Click Create.
334	334
335		-= Automated deployments with Jenkins =
	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
336	336
	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 2 ways to "migrate" the repos:
	372	+
	373	+1. You can do direct transition and edit already existing repository – choose //Target: OCI repository, //adapt the url as shown above (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The issue is that the OCI repository needs to target chart repos in the url, not the whole folder anymore.  That means if you previously deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket", other repos updates wont be working anymore and you will still need to create a new repo targeting each chartrepo.
	374	+1. Or you can add new repositories one by one taking your time, while the old chartmuseum repo will still be functioning suring migraiton. For this, you can see the next described migration process.
	375	+1. If you
	376	+
	377	+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
	378	+
	379	+(% class="box" %)
	380	+(((
	381	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
	382	+)))
	383	+
	384	+| Term | Meaning
	385	+| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
	386	+| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
	387	+
	388	+##__**Why This Migration Is Required:**__##
	389	+
	390	+* ##ChartMuseum is deprecated and will be removed.##
	391	+* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
	392	+* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
	393	+
	394	+## Migration Steps:##
	395	+
	396	+1. ##Create the New OCI Repository in Rancher##
	397	+11. Go to **Apps → Repositories**.
	398	+11. Add a new repository of type **OCI**.
	399	+11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
	400	+11. Point it to the new OCI endpoint.
	401	+1. ##Disable the Old ChartMuseum Repository Temporarily##
	402	+##This step ensures that Rancher resolves charts from the new OCI repo.##
	403	+11. Go to **Apps → Repositories**.
	404	+11. Disable the old HTTP(S)-based repository.
	405	+11. Keep it disabled until the migration is done.
	406	+1. ##Update Existing Applications to Use the New OCI Repo##
	407	+Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
	408	+11. Go to **Apps → Installed Apps**.
	409	+11. Open the application that was deployed using the old repo.
	410	+11. Click **Upgrade**.
	411	+11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
	412	+11. Choose the chart version you want to deploy (same or newer).
	413	+11. Click **Upgrade**.
	414	+1. ##Re-enable the Old Repository (Optional) ##
	415	+If you still need the old repo for other apps, re-enable it after the migration steps above.
	416	+**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
	417	+
	418	+----
	419	+
	420	+## Reverting the Migration (If Needed)
	421	+If you want to move an app back to the old repository:##
	422	+
	423	+1. Temporarily disable the new OCI repo.
	424	+1. Enable the old ChartMuseum repo.
	425	+1. Open the application → **Upgrade**.
	426	+1. Select the chart from the old repo.
	427	+1. Save.
	428	+
	429	+This will reconnect the app to the old repository.
	430	+
	431	+=
	432	+Automated deployments with Jenkins =
	433	+
337	337	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
338	338
339	339	== Prerequisites ==