Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 4.2
edited by Diana Strebkova
on 2025/12/08 15:20
Change comment: There is no comment for this version
To version 10.13
edited by Diana Strebkova
on 2025/12/12 12:06
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.
... ... @@ -178,9 +178,6 @@
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" %)
184 184  ==== Target: http(s) URL ====
185 185  
186 186  {{warning}}
... ... @@ -221,11 +221,9 @@
221 221  
222 222  [[image:Screenshot 2024-07-03 at 15.13.55.png||data-xwiki-image-style-border="true" height="149" width="785"]]
223 223  
224 -==== ====
225 -
226 226  ==== Target: OCI Repository ====
227 227  
228 -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:
229 229  
230 230  [[image:1765207154466-828.png||height="298" width="821"]]
231 231  
... ... @@ -240,7 +240,7 @@
240 240  |=(((
241 241  Name
242 242  )))|(((
243 -devops-as-a-service-helm
238 +devopsaas-jenkins-auto-agent
244 244  )))
245 245  |=(((
246 246  Description
... ... @@ -250,11 +250,17 @@
250 250  |=(((
251 251  Index URL
252 252  )))|(((
253 -oci:[[~~/~~/registry.sdc.t-systems.net/chartrepo/devopsaas-helm/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]]chartname
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}}
254 254  )))
255 255  
256 256  {{info}}
257 -Now all helm charts are accessible in harbor folders with -helm suffix. Adding the whole project doesn#t work anymore, so each separate chart should
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.**//
258 258  {{/info}}
259 259  
260 260  === Deploy Helm charts ===
... ... @@ -267,7 +267,6 @@
267 267  
268 268  == Add private chart repository ==
269 269  
270 -
271 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:
... ... @@ -280,14 +280,26 @@
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" %)
286 286  Create a new Repository by pressing the Create button.
287 287  
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 +
288 288  (% class="p1" %)
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.
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.
291 291  Choose http(s) URL to an index generated by Helm and provide the Index URL ##https:~/~/registry-<domain>.devops.t-systems.net/chartrepo/<project>/##
292 292  
293 293  (% class="p1" %)
... ... @@ -300,7 +300,61 @@
300 300  (% class="p1" %)
301 301  Click Create.
302 302  
315 +(% id="HTarget:OCIRepository-1" class="p1" %)
316 +==== Target: OCI Repository ====
303 303  
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 add the whole project, please contact support for finding a possible solution.**//
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/<chartname>##
324 +
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 +)))
329 +
330 +(% class="p1" %)
331 +For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
332 +
333 +(% class="wikigeneratedid" %)
334 +[[image:1765208347952-345.36.18.png||height="449" width="849"]]
335 +
336 +(% class="wikigeneratedid" %)
337 +Click Create.
338 +
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 chart repositories in rancher to new OCI Repository format ===
367 +
368 +As chartmuseum is getting deprecated, after the full migration the charts will be deleted from chartmuseum and old repositories won't be working in rancher anymore. For smooth migration, we recommend adding an OCI Repository along with the olf http(s) based one during migration process, as we will make the charts available in the new <pkey>-helm projects for you. If you deployed the apps using the previous chart repo, the app contains chart repo name in its labels, so transition process need few steps. First, create <chart-repo-name> OCI repo in rancher. Then disable the old repo for some time in your repositories. After that, go the the application which was deployed using the chart from older repo anf click upgrade, there you will see all available chart repository in your cluster. Scroöö till the end till you find the new repo, choose the chart with the same or different version, and click update. Now you app is connected to new oci repositories and will show upgrade sign when a new version is available. Enable the old repo if you still use it. After this process, even if a new version for the app is availalbe in old repository, you won't see it as its not connected to it anymore. To change it, repeat the previous procees in revet.
369 +
304 304  = Automated deployments with Jenkins =
305 305  
306 306  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