Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 7.1
edited by Diana Strebkova
on 2025/12/08 15:42
Change comment: There is no comment for this version
To version 10.12
edited by Diana Strebkova
on 2025/12/12 11:58
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! New approach to add chart repositories in rancher.
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.
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.
... ... @@ -220,7 +220,7 @@
220 220  
221 221  ==== Target: OCI Repository ====
222 222  
223 -To add public oci-repository, navigate to repository create button and click it.
223 +To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
224 224  
225 225  [[image:1765207154466-828.png||height="298" width="821"]]
226 226  
... ... @@ -245,13 +245,17 @@
245 245  |=(((
246 246  Index URL
247 247  )))|(((
248 -oci:[[~~/~~/registry.sdc.t-systems.net/chartrepo/devopsaas-helm/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]]chartname, for example:
248 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
249 249  
250 -oci:[[~~/~~/registry.sdc.t-systems.net/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]][[devopsaas-helm/jenkins-lib>>url:https://registry-manoni.devops.t-systems.net/harbor/projects/139/repositories/jenkins-lib]]
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}}
251 251  )))
252 252  
253 253  {{info}}
254 -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.**//
255 255  {{/info}}
256 256  
257 257  === Deploy Helm charts ===
... ... @@ -264,7 +264,6 @@
264 264  
265 265  == Add private chart repository ==
266 266  
267 -
268 268  === Create a robot account in Harbor ===
269 269  
270 270  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:
... ... @@ -277,6 +277,9 @@
277 277  
278 278  (% class="p1" %)
279 279  In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
283 +
284 +(% class="p1" %)
285 +
280 280  [[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"]]
281 281  
282 282  (% class="p1" %)
... ... @@ -283,11 +283,13 @@
283 283  Create a new Repository by pressing the Create button.
284 284  
285 285  (% id="HTarget:http28s29URL-1" class="p1" %)
286 -==== [[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"]]
287 -Target: http(s) URL ====
292 +==== [[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"]] ====
288 288  
294 +(% id="HTarget:http28s29URL-1" class="p1" %)
295 +==== Target: http(s) URL ====
296 +
289 289  {{warning title="Chartmuseum Deprecation"}}
290 -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.
291 291  {{/warning}}
292 292  
293 293  (% class="p1" %)
... ... @@ -304,17 +304,20 @@
304 304  (% class="p1" %)
305 305  Click Create.
306 306  
315 +(% id="HTarget:OCIRepository-1" class="p1" %)
307 307  ==== Target: OCI Repository ====
308 308  
309 309  {{info}}
310 -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.**//
311 311  {{/info}}
312 312  
313 313  (% class="p1" %)
314 -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>##
315 315  
316 -(% class="p1" %)
317 -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 +)))
318 318  
319 319  (% class="p1" %)
320 320  For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
... ... @@ -325,6 +325,35 @@
325 325  (% class="wikigeneratedid" %)
326 326  Click Create.
327 327  
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 ===
367 +
328 328  = Automated deployments with Jenkins =
329 329  
330 330  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
© 2018-2025 T-Systems International GmbH