Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 10.6
edited by Diana Strebkova
on 2025/12/12 11:48
on 2025/12/12 11:48
Change comment:
There is no comment for this version
To version 10.12
edited by Diana Strebkova
on 2025/12/12 11:58
on 2025/12/12 11:58
Change comment:
There is no comment for this version
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,6 +280,9 @@ 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 + 283 283 [[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"]] 284 284 285 285 (% class="p1" %) ... ... @@ -292,7 +292,7 @@ 292 292 ==== Target: http(s) URL ==== 293 293 294 294 {{warning title="Chartmuseum Deprecation"}} 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. 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. 296 296 {{/warning}} 297 297 298 298 (% class="p1" %) ... ... @@ -313,14 +313,16 @@ 313 313 ==== Target: OCI Repository ==== 314 314 315 315 {{info}} 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. 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.**// 317 317 {{/info}} 318 318 319 319 (% class="p1" %) 320 -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>## 321 321 322 -(% class="p1" %) 323 -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 +))) 324 324 325 325 (% class="p1" %) 326 326 For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section. ... ... @@ -331,6 +331,35 @@ 331 331 (% class="wikigeneratedid" %) 332 332 Click Create. 333 333 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 + 334 334 = Automated deployments with Jenkins = 335 335 336 336 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.