Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 10.4
edited by Diana Strebkova
on 2025/12/12 11:45
on 2025/12/12 11:45
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
-
... ... @@ -245,19 +245,17 @@ 245 245 |=((( 246 246 Index URL 247 247 )))|((( 248 -oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/chartname, for example: 248 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example: 249 249 250 250 oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib 251 251 252 252 {{info}} 253 -T ypeyourinformation message here.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 254 {{/info}} 255 - 256 - 257 257 ))) 258 258 259 259 {{info}} 260 -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.**// 261 261 {{/info}} 262 262 263 263 === Deploy Helm charts === ... ... @@ -270,7 +270,6 @@ 270 270 271 271 == Add private chart repository == 272 272 273 - 274 274 === Create a robot account in Harbor === 275 275 276 276 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: ... ... @@ -283,6 +283,9 @@ 283 283 284 284 (% class="p1" %) 285 285 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 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. 299 299 {{/warning}} 300 300 301 301 (% class="p1" %) ... ... @@ -316,14 +316,16 @@ 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. 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" %) 323 -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>## 324 324 325 -(% class="p1" %) 326 -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 +))) 327 327 328 328 (% class="p1" %) 329 329 For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section. ... ... @@ -334,6 +334,35 @@ 334 334 (% class="wikigeneratedid" %) 335 335 Click Create. 336 336 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 + 337 337 = Automated deployments with Jenkins = 338 338 339 339 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.