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,9 @@
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	+(% class="p1" %)
	285	+
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.
	298	+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.
	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.**//
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>##
	323	+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.
	325	+(% class="box" %)
	326	+(((
	327	+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.
	328	+)))
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,6 +332,37 @@
332	332	(% class="wikigeneratedid" %)
333	333	Click Create.
334	334
	339	+
	340	+(% class="wrapped" %)
	341	+|=(((
	342	+Field
	343	+)))|=(((
	344	+Value
	345	+)))
	346	+|=(((
	347	+Name
	348	+)))|(((
	349	+sdcloud-sdportal
	350	+)))
	351	+|=(((
	352	+Description
	353	+)))|(((
	354	+Sdportal charts of sdcloud project
	355	+)))
	356	+|=(((
	357	+Index URL
	358	+)))|(((
	359	+oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
	360	+
	361	+{{info}}
	362	+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.
	363	+{{/info}}
	364	+)))
	365	+
	366	+=== Migrating chart repositories in rancher to new OCI Repository format ===
	367	+
	368	+As chartmuseum is getting deprecated, after the full migration the charts will be deleted from chartmuseum and old repositories won't be working in rancher anymore. For smooth migration, we recommend adding an OCI Repository along with the olf http(s) based one during migration process, as we will make the charts available in the new <pkey>-helm projects for you. If you deployed the apps using the previous chart repo, the app contains chart repo name in its labels, so transition process need few steps. First, create <chart-repo-name> OCI repo in rancher. Then disable the old repo for some time in your repositories. After that, go the the application which was deployed using the chart from older repo anf click upgrade, there you will see all available chart repository in your cluster. Scroöö till the end till you find the new repo, choose the chart with the same or different version, and click update. Now you app is connected to new oci repositories and will show upgrade sign when a new version is available. Enable the old repo if you still use it. After this process, even if a new version for the app is availalbe in old repository, you won't see it as its not connected to it anymore. To change it, repeat the previous procees in revet.
	369	+
335	335	= Automated deployments with Jenkins =
336	336
337	337	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.