Changes for page Rancher 2

Summary

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

Details

Page properties

Content

...	...	@@ -316,7 +316,7 @@
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.**//
	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.**//
320	320	{{/info}}
321	321
322	322	(% class="p1" %)
...	...	@@ -346,27 +346,25 @@
346	346	|=(((
347	347	Name
348	348	)))|(((
349		-sdcloud-sdportal
	349	+devopsaas-jenkins-auto-agent
350	350	)))
351	351	|=(((
352	352	Description
353	353	)))|(((
354		-Sdportal charts of sdcloud project
	354	+Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
355	355	)))
356	356	|=(((
357	357	Index URL
358	358	)))|(((
359		-oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
	359	+oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
360	360
	361	+oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
	362	+
361	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.
	364	+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.
363	363	{{/info}}
364	364	)))
365	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.