Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 10.5
edited by Diana Strebkova
on 2025/12/12 11:47
Change comment: There is no comment for this version
To version 2.2
edited by Diana Strebkova
on 2025/12/08 15:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -159,7 +159,7 @@
159 159  == Add public helm chart ==
160 160  
161 161  {{warning width="70" title="Chartmuseum Deprecation"}}
162 -Chartmuseum is deprecated in new Harbor versions, we are migrating all helm charts to oci-compatible repositories in Harbor with "PKEY-helm" naming convention. For internal harbor repos, use new approach to add OCI chart repositories in rancher.
162 +Chartmuseum is deprecated in new Harbor versions, we are migrating all helm charts to oci-compatible repositories in Harbor! New approach to add chart repositories in rancher.
163 163  {{/warning}}
164 164  
165 165  In this section, we describe (% style="color:#172b4d" %)how to add public helm charts like the one of DevOps-as-a-Service to a cluster to allow manual deployments.
... ... @@ -178,6 +178,9 @@
178 178  [[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]]
179 179  
180 180  (% id="H" class="p1" %)
181 +==== ====
182 +
183 +(% id="HTarget:http28s29URL" class="p1" %)
181 181  ==== Target: http(s) URL ====
182 182  
183 183  {{warning}}
... ... @@ -218,12 +218,16 @@
218 218  
219 219  [[image:Screenshot 2024-07-03 at 15.13.55.png||data-xwiki-image-style-border="true" height="149" width="785"]]
220 220  
224 +==== ====
225 +
221 221  ==== Target: OCI Repository ====
222 222  
223 -To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
228 +To add public oci-repository, navigate to repository create button and click it.
224 224  
225 -[[image:1765207154466-828.png||height="298" width="821"]]
230 +[[image:1765206888644-487.png||height="320" width="907"]]
226 226  
232 +
233 +(% class="p1" %)
227 227  In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
228 228  
229 229  (% class="wrapped" %)
... ... @@ -235,7 +235,7 @@
235 235  |=(((
236 236  Name
237 237  )))|(((
238 -devopsaas-jenkins-auto-agent
245 +devops-as-a-service-helm
239 239  )))
240 240  |=(((
241 241  Description
... ... @@ -245,19 +245,11 @@
245 245  |=(((
246 246  Index URL
247 247  )))|(((
248 -oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
249 -
250 -oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
251 -
252 -{{info}}
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 -{{/info}}
255 +[[https:~~/~~/registry.sdc.t-systems.net/chartrepo/devopsaas/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]]
255 255  )))
256 256  
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
259 -{{/info}}
260 260  
259 +
261 261  === Deploy Helm charts ===
262 262  
263 263  Now go to Apps>Charts and filter if necessary for the devops-as-a-service Helm chart repository. Like shown below, a list of available charts is displayed. Simply click on one of the tiles to deploy them to your cluster.
... ... @@ -286,18 +286,9 @@
286 286  (% class="p1" %)
287 287  Create a new Repository by pressing the Create button.
288 288  
289 -(% id="HTarget:http28s29URL-1" class="p1" %)
290 -==== [[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]] ====
291 -
292 -(% id="HTarget:http28s29URL-1" class="p1" %)
293 -==== Target: http(s) URL ====
294 -
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 -{{/warning}}
298 -
299 299  (% class="p1" %)
300 -A name for the Repository has to be set. In the screenshot, the project name CITEST is used, which corresponds to our example from above.
289 +[[image:attach:Screenshot 2023-04-25 at 13.30.33.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="127" width="1100"]]
290 +\\A name for the Repository has to be set. In the screenshot, the project name CITEST is used, which corresponds to our example from above.
301 301  Choose http(s) URL to an index generated by Helm and provide the Index URL ##https:~/~/registry-<domain>.devops.t-systems.net/chartrepo/<project>/##
302 302  
303 303  (% class="p1" %)
... ... @@ -310,28 +310,7 @@
310 310  (% class="p1" %)
311 311  Click Create.
312 312  
313 -(% id="HTarget:OCIRepository-1" class="p1" %)
314 -==== Target: OCI Repository ====
315 315  
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 -{{/info}}
319 -
320 -(% class="p1" %)
321 -Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chatname>##
322 -
323 -(% class="p1" %)
324 -Replace ##<domain>## , ##<project>##  and ##<chatname> ##as necessary to match your set-up.
325 -
326 -(% class="p1" %)
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.
328 -
329 -(% class="wikigeneratedid" %)
330 -[[image:1765208347952-345.36.18.png||height="449" width="849"]]
331 -
332 -(% class="wikigeneratedid" %)
333 -Click Create.
334 -
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.
1765207032873-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -142.1 KB
Content
1765207154466-828.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -143.6 KB
Content
1765208347952-345.36.18.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -199.3 KB
Content
© 2018-2025 T-Systems International GmbH