Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 5.1
edited by Diana Strebkova
on 2025/12/08 15:28
Change comment: There is no comment for this version
To version 10.7
edited by Diana Strebkova
on 2025/12/12 11:49
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,14 +277,26 @@
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 283  Create a new Repository by pressing the Create button.
284 284  
291 +(% id="HTarget:http28s29URL-1" class="p1" %)
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"]] ====
293 +
294 +(% id="HTarget:http28s29URL-1" class="p1" %)
295 +==== Target: http(s) URL ====
296 +
297 +{{warning title="Chartmuseum Deprecation"}}
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 +{{/warning}}
300 +
285 285  (% 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 -\\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.
302 +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.
288 288  Choose http(s) URL to an index generated by Helm and provide the Index URL ##https:~/~/registry-<domain>.devops.t-systems.net/chartrepo/<project>/##
289 289  
290 290  (% class="p1" %)
... ... @@ -297,7 +297,28 @@
297 297  (% class="p1" %)
298 298  Click Create.
299 299  
315 +(% id="HTarget:OCIRepository-1" class="p1" %)
316 +==== Target: OCI Repository ====
300 300  
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 a
320 +{{/info}}
321 +
322 +(% class="p1" %)
323 +Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chatname>##
324 +
325 +(% class="p1" %)
326 +Replace ##<domain>## , ##<project>##  and ##<chatname> ##as necessary to match your set-up.
327 +
328 +(% class="p1" %)
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.
330 +
331 +(% class="wikigeneratedid" %)
332 +[[image:1765208347952-345.36.18.png||height="449" width="849"]]
333 +
334 +(% class="wikigeneratedid" %)
335 +Click Create.
336 +
301 301  = Automated deployments with Jenkins =
302 302  
303 303  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
1765208347952-345.36.18.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +199.3 KB
Content
© 2018-2025 T-Systems International GmbH