Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -268,7 +268,7 @@
268	268
269	269	== Add private chart repository ==
270	270
271		-=== Create a robot account in Harbor ===
	271	+Create a robot account in Harbor
272	272
273	273	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:
274	274
...	...	@@ -280,9 +280,6 @@
280	280
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		-
284		-(% class="p1" %)
285		-
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 internal harbor repositories to Rancher that way anymore. Instead use Target: OCI repository.
	295	+Chartmuseum in Harbor is deprecated, meaning we won't be able to add repositories to Rancher that way anymore. Instead use Target: OCI repository.
299	299	{{/warning}}
300	300
301	301	(% class="p1" %)
...	...	@@ -316,16 +316,14 @@
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.//** If you have a real need to add the whole project, please contact support for finding a possible solution.**//
	316	+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.
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/<chartname>##
	320	+Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chatname>##
324	324
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		-)))
	322	+(% class="p1" %)
	323	+Replace ##<domain>## , ##<project>##  and ##<chatname> ##as necessary to match your set-up.
329	329
330	330	(% class="p1" %)
331	331	For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
...	...	@@ -336,37 +336,6 @@
336	336	(% class="wikigeneratedid" %)
337	337	Click Create.
338	338
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		-
370	370	= Automated deployments with Jenkins =
371	371
372	372	In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.