Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -245,19 +245,17 @@
245	245	|=(((
246	246	Index URL
247	247	)))|(((
248		-oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/chartname, for example:
	248	+oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
249	249
250	250	oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
251	251
252	252	{{info}}
253		-Type your information message here.
	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	254	{{/info}}
255		-
256		-
257	257	)))
258	258
259	259	{{info}}
260		-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.
	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.**//
261	261	{{/info}}
262	262
263	263	=== Deploy Helm charts ===
...	...	@@ -270,7 +270,6 @@
270	270
271	271	== Add private chart repository ==
272	272
273		-
274	274	=== Create a robot account in Harbor ===
275	275
276	276	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:
...	...	@@ -283,6 +283,8 @@
283	283
284	284	(% class="p1" %)
285	285	In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
	283	+
	284	+
286	286	[[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"]]
287	287
288	288	(% class="p1" %)
...	...	@@ -295,7 +295,7 @@
295	295	==== Target: http(s) URL ====
296	296
297	297	{{warning title="Chartmuseum Deprecation"}}
298		-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.
299	299	{{/warning}}
300	300
301	301	(% class="p1" %)
...	...	@@ -316,14 +316,16 @@
316	316	==== Target: OCI Repository ====
317	317
318	318	{{info}}
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.
	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.**//
320	320	{{/info}}
321	321
322	322	(% class="p1" %)
323		-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>##
324	324
325		-(% class="p1" %)
326		-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	+)))
327	327
328	328	(% class="p1" %)
329	329	For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
...	...	@@ -334,6 +334,108 @@
334	334	(% class="wikigeneratedid" %)
335	335	Click Create.
336	336
	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
	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	+To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
	372	+
	373	+(% class="box" %)
	374	+(((
	375	+**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
	376	+)))
	377	+
	378	+| Term | Meaning
	379	+| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
	380	+| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
	381	+
	382	+##__**Why This Migration Is Required:**__##
	383	+
	384	+* ##ChartMuseum is deprecated and will be removed.##
	385	+* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
	386	+* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
	387	+
	388	+## Migration Steps:##
	389	+
	390	+1. ##Create the New OCI Repository in Rancher##
	391	+11. Go to **Apps → Repositories**.
	392	+11. Add a new repository of type **OCI**.
	393	+11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
	394	+11. Point it to the new OCI endpoint.
	395	+1. ##Disable the Old ChartMuseum Repository Temporarily##. ##This step ensures that Rancher resolves charts from the new OCI repo.##
	396	+11. Go to **Apps → Repositories**.
	397	+11. Disable the old HTTP(S)-based repository.
	398	+11. Keep it disabled until the migration is done.
	399	+1. ##Update Existing Applications to Use the New OCI Repo##
	400	+##Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.##
	401	+11. Go to **Apps → Installed Apps**.
	402	+11. Open the application that was deployed using the old repo.
	403	+11. Click **Upgrade**.
	404	+11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
	405	+11. Choose the chart version you want to deploy (same or newer).
	406	+11. Click **Upgrade**.
	407	+1. ##Re-enable the Old Repository (Optional) If you still need the old repo for other apps, re-enable it after the migration steps above.##
	408	+
	409	+ 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.
	410	+
	411	+-----
	412	+
	413	+## Reverting the Migration (If Needed)
	414	+If you want to move an app back to the old repository:##
	415	+
	416	+1. Temporarily disable the new OCI repo.
	417	+2. Enable the old ChartMuseum repo.
	418	+3. Open the application → **Upgrade**.
	419	+4. Select the chart from the old repo.
	420	+5. Save.
	421	+
	422	+This will reconnect the app to the old repository.
	423	+
	424	+-----
	425	+
	426	+## Summary
	427	+- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
	428	+- After upgrade, apps no longer track versions from the old repository.
	429	+- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.##
	430	+
	431	+-----
	432	+
	433	+If you want, I can also generate:
	434	+- a shorter version (1-pager),
	435	+- a diagram,
	436	+- a Rancher UI screenshot guide,
	437	+- or a version tailored for your team’s internal wiki.
	438	+
	439	+
337	337	= Automated deployments with Jenkins =
338	338
339	339	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.