Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2026/04/20 09:21
From version 10.2
edited by Diana Strebkova
on 2025/12/12 11:41
Change comment: There is no comment for this version
To version 24.2
edited by Diana Strebkova
on 2026/04/20 09:12
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 with "PKEY-helm naming convention. For internal harbor repos, use new approach to add OCI 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.
... ... @@ -177,51 +177,8 @@
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 ====
180 +To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
182 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 -(% class="p1" %)
188 -In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
189 -
190 -(% class="wrapped" %)
191 -|=(((
192 -Field
193 -)))|=(((
194 -Value
195 -)))
196 -|=(((
197 -Name
198 -)))|(((
199 -devops-as-a-service
200 -)))
201 -|=(((
202 -Description
203 -)))|(((
204 -Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
205 -)))
206 -|=(((
207 -Index URL
208 -)))|(((
209 -[[https:~~/~~/registry.sdc.t-systems.net/chartrepo/devopsaas/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]]
210 -)))
211 -
212 -[[image:attach:image-2024-2-27_14-29-17.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="540"]]
213 -
214 -(% class="p1" %)
215 -Finally, click Create.
216 -
217 -The repository is now listed:
218 -
219 -[[image:Screenshot 2024-07-03 at 15.13.55.png||data-xwiki-image-style-border="true" height="149" width="785"]]
220 -
221 -==== Target: OCI Repository ====
222 -
223 -To add public oci-repository, navigate to repository create button and click it.
224 -
225 225  [[image:1765207154466-828.png||height="298" width="821"]]
226 226  
227 227  In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
... ... @@ -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:
205 +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]]
207 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-auto-agent
208 +
209 +{{box}}
210 +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 is not supported in rancher.
211 +{{/box}}
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.
215 +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,19 +277,21 @@
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.
240 +
241 +
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  
285 -(% id="HTarget:http28s29URL-1" 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"]] ====
247 +(% class="p1" id="HTarget:http28s29URL-1" %)
248 +[[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 287  
288 288  (% id="HTarget:http28s29URL-1" class="p1" %)
289 289  ==== Target: http(s) URL ====
290 290  
291 291  {{warning title="Chartmuseum Deprecation"}}
292 -Chartmuseum in Harbor is deprecated, meaning we won't be able to add repositories to Rancher that way anymore. Instead use Target: OCI repository.
254 +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.
293 293  {{/warning}}
294 294  
295 295  (% class="p1" %)
... ... @@ -310,14 +310,16 @@
310 310  ==== Target: OCI Repository ====
311 311  
312 312  {{info}}
313 -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.
275 +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.**//
314 314  {{/info}}
315 315  
316 316  (% class="p1" %)
317 -Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chatname>##
279 +Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chartname>##
318 318  
319 -(% class="p1" %)
320 -Replace ##<domain>## , ##<project>##  and ##<chatname> ##as necessary to match your set-up.
281 +(% class="box" %)
282 +(((
283 +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.
284 +)))
321 321  
322 322  (% class="p1" %)
323 323  For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
... ... @@ -328,6 +328,114 @@
328 328  (% class="wikigeneratedid" %)
329 329  Click Create.
330 330  
295 +(% class="wrapped" %)
296 +|=(((
297 +Field
298 +)))|=(((
299 +Value
300 +)))
301 +|=(((
302 +Name
303 +)))|(((
304 +sdcloud-sdportal
305 +)))
306 +|=(((
307 +Description
308 +)))|(((
309 +Sdportal charts of sdcloud project
310 +)))
311 +|=(((
312 +Index URL
313 +)))|(((
314 +oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
315 +
316 +{{info}}
317 +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.
318 +{{/info}}
319 +)))
320 +
321 +== Migrating chart repositories in rancher to new OCI Repository format ==
322 +
323 +(% class="box warningmessage" %)
324 +(((
325 +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)**.
326 +)))
327 +
328 +(% class="box" %)
329 +(((
330 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. During migration, please adapt your helm push commands and url's for new oci-compatible repository.**
331 +)))
332 +
333 +There are two ways to migrate your repositories:
334 +
335 +1. ##Direct Transition (Editing the Existing Repository)##
336 +1*. Change the target to “OCI Repository”.
337 +1*. Update the URL as required (the repository name cannot be changed), check **Target: OCI Repository** documentation above
338 +1*. After saving, installed apps will automatically start using the updated repository.
339 +1*. (% class="box" %)
340 +(((
341 +Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
342 +If your old repository included several charts (for example “bitbucket” and “jira”), then after switching to OCI you can only target one chart (e.g. “bitbucket”).
343 +The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
344 +)))
345 +1. Add New Repositories One by One (Recommended), preserve the old one till the end. This approach allows a smooth transition while the old ChartMuseum repository continues to function. You can:
346 +1*. Create a new OCI repository for each chart,
347 +1*. Keep the old ChartMuseum repo enabled during the migration,
348 +1*. Migrate applications gradually following the steps described here.
349 +1*. This avoids disruptions and allows controlled migration.
350 +
351 +1. //Special Case: Old Repo Targeting Multiple Chart Repos//
352 +If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
353 +
354 +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
355 +
356 +| Term | Meaning
357 +| **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
358 +| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
359 +
360 +##__**Why This Migration Is Required:**__##
361 +
362 +* ##ChartMuseum is deprecated and will be removed.##
363 +* ##Applications deployed from old repos keep a reference to that repo inside their labels.##
364 +* ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
365 +
366 +## Migration Steps:##
367 +
368 +1. ##Create the New OCI Repository in Rancher##
369 +11. Go to **Apps → Repositories**.
370 +11. Add a new repository of type **OCI**.
371 +11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). __**You can't name it the same and can't rename it later.**__
372 +11. Point it to the new OCI endpoint.
373 +1. ##Disable the Old ChartMuseum Repository Temporarily## 
374 +##This step ensures that Rancher resolves charts from the new OCI repo.##
375 +11. Go to **Apps → Repositories**.
376 +11. Disable the old HTTP(S)-based repository.
377 +11. Keep it disabled until the migration is done.
378 +[[image:1765548124989-482.59.06.png||height="152" width="485"]]
379 +1. ##Update Existing Applications to Use the New OCI Repo##
380 +Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
381 +11. Go to **Apps → Installed Apps**.
382 +11. Open the application that was deployed using the old repo.
383 +11. Click **Edit/Upgrade**.
384 +[[image:1765548598644-830.png||height="138" width="811"]]
385 +11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**. Or enter the chart name in search bar:
386 +[[image:1765548750604-334.png||height="293" width="308"]]
387 +11. Choose the chart version you want to deploy (same or newer).
388 +11. Click **Upgrade**.
389 +1. ##Re-enable the Old Repository (Optional) ##
390 +If you still need the old repo for other apps, re-enable it after the migration steps above.
391 +**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
392 +
393 +##If you want to move an app back to the old repository:##
394 +
395 +1. Temporarily disable the new OCI repo.
396 +1. Enable the old ChartMuseum repo.
397 +1. Open the application → **Upgrade**.
398 +1. Select the chart from the old repo.
399 +1. Save.
400 +
401 +This will reconnect the app to the old repository.
402 +
331 331  = Automated deployments with Jenkins =
332 332  
333 333  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
1765548124989-482.59.06.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +64.4 KB
Content
1765548598644-830.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +153.4 KB
Content
1765548750604-334.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +103.0 KB
Content
© 2018-2026 T-Systems International GmbH