Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 12.6
edited by Diana Strebkova
on 2025/12/12 13:00
Change comment: There is no comment for this version
To version 1.1
edited by DOaaS Operator
on 2025/02/05 11:33
Change comment: Imported from XAR

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
1 +xwiki:XWiki.sdcloud-admin-0
Content
... ... @@ -156,12 +156,8 @@
156 156  
157 157  = Helm charts =
158 158  
159 -== Add public helm chart ==
159 +== Add public helm charts ==
160 160  
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 with "PKEY-helm" naming convention. For internal harbor repos, use new approach to add OCI chart repositories in rancher.
163 -{{/warning}}
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.
166 166  
167 167  (% id="HCreateAppRepositoryinRancher" class="p1" %)
... ... @@ -177,13 +177,6 @@
177 177  (% class="p1" %)
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 -(% id="H" class="p1" %)
181 -==== Target: http(s) URL ====
182 -
183 -{{warning}}
184 -This example is being deprecated, you can still add other external repositories in that way, but all internal harbor-hosted repositories should be added as Target: OCI Repository
185 -{{/warning}}
186 -
187 187  (% class="p1" %)
188 188  In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
189 189  
... ... @@ -218,46 +218,6 @@
218 218  
219 219  [[image:Screenshot 2024-07-03 at 15.13.55.png||data-xwiki-image-style-border="true" height="149" width="785"]]
220 220  
221 -==== Target: OCI Repository ====
222 -
223 -To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
224 -
225 -[[image:1765207154466-828.png||height="298" width="821"]]
226 -
227 -In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
228 -
229 -(% class="wrapped" %)
230 -|=(((
231 -Field
232 -)))|=(((
233 -Value
234 -)))
235 -|=(((
236 -Name
237 -)))|(((
238 -devopsaas-jenkins-auto-agent
239 -)))
240 -|=(((
241 -Description
242 -)))|(((
243 -Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
244 -)))
245 -|=(((
246 -Index URL
247 -)))|(((
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}}
255 -)))
256 -
257 -{{info}}
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.**//
259 -{{/info}}
260 -
261 261  === Deploy Helm charts ===
262 262  
263 263  Now go to Apps>Charts and filter if necessary for the devops-as-a-service Helm chart repository. Like shown below, a list of available charts is displayed. Simply click on one of the tiles to deploy them to your cluster.
... ... @@ -268,6 +268,7 @@
268 268  
269 269  == Add private chart repository ==
270 270  
220 +
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,25 +280,14 @@
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 -
285 285  [[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"]]
286 286  
287 287  (% class="p1" %)
288 288  Create a new Repository by pressing the Create button.
289 289  
290 -(% id="HTarget:http28s29URL-1" class="p1" %)
291 -==== [[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"]] ====
292 -
293 -(% id="HTarget:http28s29URL-1" class="p1" %)
294 -==== Target: http(s) URL ====
295 -
296 -{{warning title="Chartmuseum Deprecation"}}
297 -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.
298 -{{/warning}}
299 -
300 300  (% class="p1" %)
301 -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.
239 +[[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"]]
240 +\\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 302  Choose http(s) URL to an index generated by Helm and provide the Index URL ##https:~/~/registry-<domain>.devops.t-systems.net/chartrepo/<project>/##
303 303  
304 304  (% class="p1" %)
... ... @@ -311,124 +311,9 @@
311 311  (% class="p1" %)
312 312  Click Create.
313 313  
314 -(% id="HTarget:OCIRepository-1" class="p1" %)
315 -==== Target: OCI Repository ====
316 316  
317 -{{info}}
318 -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.**//
319 -{{/info}}
254 += Automated deployments with Jenkins =
320 320  
321 -(% class="p1" %)
322 -Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chartname>##
323 -
324 -(% class="box" %)
325 -(((
326 -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.
327 -)))
328 -
329 -(% class="p1" %)
330 -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 -
332 -(% class="wikigeneratedid" %)
333 -[[image:1765208347952-345.36.18.png||height="449" width="849"]]
334 -
335 -(% class="wikigeneratedid" %)
336 -Click Create.
337 -
338 -(% class="wrapped" %)
339 -|=(((
340 -Field
341 -)))|=(((
342 -Value
343 -)))
344 -|=(((
345 -Name
346 -)))|(((
347 -sdcloud-sdportal
348 -)))
349 -|=(((
350 -Description
351 -)))|(((
352 -Sdportal charts of sdcloud project
353 -)))
354 -|=(((
355 -Index URL
356 -)))|(((
357 -oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
358 -
359 -{{info}}
360 -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.
361 -{{/info}}
362 -)))
363 -
364 -=== Migrating chart repositories in rancher to new OCI Repository format ===
365 -
366 -(% class="box warningmessage" %)
367 -(((
368 -ChartMuseum is being deprecated. After the migration is complete, **all harbor charts will be removed from ChartMuseum**, and **old HTTP(S)-based chart repositories will no longer work in Rancher (for internal harbor charts)**.
369 -)))
370 -
371 -There are 2 ways to "migrate" the repos:
372 -
373 -1.
374 -
375 -To ensure a smooth transition, we recommend to **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. If you don't w
376 -
377 -(% class="box" %)
378 -(((
379 -**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
380 -)))
381 -
382 -| Term | Meaning
383 -| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
384 -| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
385 -
386 -##__**Why This Migration Is Required:**__##
387 -
388 -* ##ChartMuseum is deprecated and will be removed.##
389 -* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
390 -* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
391 -
392 -## Migration Steps:##
393 -
394 -1. ##Create the New OCI Repository in Rancher##
395 -11. Go to **Apps → Repositories**.
396 -11. Add a new repository of type **OCI**.
397 -11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
398 -11. Point it to the new OCI endpoint.
399 -1. ##Disable the Old ChartMuseum Repository Temporarily## 
400 -##This step ensures that Rancher resolves charts from the new OCI repo.##
401 -11. Go to **Apps → Repositories**.
402 -11. Disable the old HTTP(S)-based repository.
403 -11. Keep it disabled until the migration is done.
404 -1. ##Update Existing Applications to Use the New OCI Repo##
405 -Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
406 -11. Go to **Apps → Installed Apps**.
407 -11. Open the application that was deployed using the old repo.
408 -11. Click **Upgrade**.
409 -11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
410 -11. Choose the chart version you want to deploy (same or newer).
411 -11. Click **Upgrade**.
412 -1. ##Re-enable the Old Repository (Optional) ##
413 -If you still need the old repo for other apps, re-enable it after the migration steps above.
414 -**Note:** Even if a newer chart version exists in the old repository, your migrated app **will not see it**, because it is no longer connected to that repo
415 -
416 -----
417 -
418 -## Reverting the Migration (If Needed)
419 -If you want to move an app back to the old repository:##
420 -
421 -1. Temporarily disable the new OCI repo.
422 -1. Enable the old ChartMuseum repo.
423 -1. Open the application → **Upgrade**.
424 -1. Select the chart from the old repo.
425 -1. Save.
426 -
427 -This will reconnect the app to the old repository.
428 -
429 -=
430 -Automated deployments with Jenkins =
431 -
432 432  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
433 433  
434 434  == Prerequisites ==
1765206888644-487.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -142.4 KB
Content
1765207032873-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -142.1 KB
Content
1765207154466-828.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -143.6 KB
Content
1765208347952-345.36.18.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -199.3 KB
Content
© 2018-2025 T-Systems International GmbH