Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2026/04/20 09:21
From version 20.1
edited by Diana Strebkova
on 2025/12/12 14:21
Change comment: There is no comment for this version
To version 28.1
edited by Diana Strebkova
on 2026/04/20 09:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -158,10 +158,6 @@
158 158  
159 159  == Add public helm chart ==
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,49 +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 -(% 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 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"]]
... ... @@ -247,7 +247,7 @@
247 247  )))|(((
248 248  oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
249 249  
250 -oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
203 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-auto-agent
251 251  
252 252  {{box}}
253 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 is not supported in rancher.
... ... @@ -272,7 +272,7 @@
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:
274 274  
275 -* Read Helm Chart
228 +* Read Artifact
276 276  * Pull Repository
277 277  
278 278  (% id="HCreateAppRepositoryinRancher-1" class="p1" %)
... ... @@ -281,7 +281,6 @@
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 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" %)
... ... @@ -291,29 +291,7 @@
291 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 292  
293 293  (% id="HTarget:http28s29URL-1" class="p1" %)
294 -==== Target: http(s) URL ====
295 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 -(% 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.
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 -
304 -(% class="p1" %)
305 -Replace ##<domain>## and ##<project>## as necessary to match your set-up.
306 -
307 -(% class="p1" %)
308 -For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
309 -[[image:attach:Screenshot 2023-04-26 at 18.10.15.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="468" width="1100"]]
310 -
311 -(% class="p1" %)
312 -Click Create.
313 -
314 -(% id="HTarget:OCIRepository-1" class="p1" %)
315 -==== Target: OCI Repository ====
316 -
317 317  {{info}}
318 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 319  {{/info}}
... ... @@ -361,16 +361,16 @@
361 361  {{/info}}
362 362  )))
363 363  
364 -=== Migrating chart repositories in rancher to new OCI Repository format ===
294 +== Migrating chart repositories in rancher to new OCI Repository format ==
365 365  
366 366  (% class="box warningmessage" %)
367 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)**.
298 +ChartMuseum is deprecated. **All harbor charts are removed from ChartMuseum**, and **old HTTP(S)-based chart repositories no longer work in Rancher (for internal harbor charts)**.
369 369  )))
370 370  
371 371  (% class="box" %)
372 372  (((
373 -**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.**
303 +**All your charts are available in the corresponding  `<pkey>-helm` OCI project.**
374 374  )))
375 375  
376 376  There are two ways to migrate your repositories:
... ... @@ -377,7 +377,7 @@
377 377  
378 378  1. ##Direct Transition (Editing the Existing Repository)##
379 379  1*. Change the target to “OCI Repository”.
380 -1*. Update the URL as required (the repository name cannot be changed).
310 +1*. Update the URL as required (the repository name cannot be changed) and add a new robot account for helm project, check documentation above
381 381  1*. After saving, installed apps will automatically start using the updated repository.
382 382  1*. (% class="box" %)
383 383  (((
... ... @@ -390,11 +390,10 @@
390 390  1*. Keep the old ChartMuseum repo enabled during the migration,
391 391  1*. Migrate applications gradually following the steps described here.
392 392  1*. This avoids disruptions and allows controlled migration.
323 +
393 393  1. //Special Case: Old Repo Targeting Multiple Chart Repos//
394 394  If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
395 395  
396 -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
397 -
398 398  | Term | Meaning
399 399  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
400 400  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -401,7 +401,7 @@
401 401  
402 402  ##__**Why This Migration Is Required:**__##
403 403  
404 -* ##ChartMuseum is deprecated and will be removed.##
333 +* ##ChartMuseum is deprecated.##
405 405  * ##Applications deployed from old repos keep a reference to that repo inside their labels.##
406 406  * ##Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions from new repository**.##
407 407  
... ... @@ -432,8 +432,7 @@
432 432  If you still need the old repo for other apps, re-enable it after the migration steps above.
433 433  **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
434 434  
435 -##
436 -If you want to move an app back to the old repository:##
364 +##If you want to move an app back to the old repository:##
437 437  
438 438  1. Temporarily disable the new OCI repo.
439 439  1. Enable the old ChartMuseum repo.
... ... @@ -443,8 +443,7 @@
443 443  
444 444  This will reconnect the app to the old repository.
445 445  
446 -=
447 -Automated deployments with Jenkins =
374 += Automated deployments with Jenkins =
448 448  
449 449  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
450 450  
© 2018-2026 T-Systems International GmbH