Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2026/04/20 09:21
From version 11.1
edited by Diana Strebkova
on 2025/12/12 12:08
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
... ... @@ -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,11 +247,11 @@
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
207 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-auto-agent
251 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}}
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}}
255 255  )))
256 256  
257 257  {{info}}
... ... @@ -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 -(% class="p1" %)
285 285  
286 286  [[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"]]
287 287  
... ... @@ -288,8 +288,8 @@
288 288  (% class="p1" %)
289 289  Create a new Repository by pressing the Create button.
290 290  
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"]] ====
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"]]
293 293  
294 294  (% id="HTarget:http28s29URL-1" class="p1" %)
295 295  ==== Target: http(s) URL ====
... ... @@ -336,7 +336,6 @@
336 336  (% class="wikigeneratedid" %)
337 337  Click Create.
338 338  
339 -
340 340  (% class="wrapped" %)
341 341  |=(((
342 342  Field
... ... @@ -363,103 +363,88 @@
363 363  {{/info}}
364 364  )))
365 365  
366 -=== Migrating chart repositories in rancher to new OCI Repository format ===
321 +== Migrating chart repositories in rancher to new OCI Repository format ==
367 367  
368 -# Migration Guide: ChartMuseum → OCI-based Chart Repositories in Rancher
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 +)))
369 369  
370 -## Overview
371 -ChartMuseum is being deprecated. After the migration is complete, **all charts will be removed from ChartMuseum**, and **old HTTP(S)-based chart repositories will no longer work in Rancher**.
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 +)))
372 372  
373 -To ensure a smooth transition, each project should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
333 +There are two ways to migrate your repositories:
374 374  
375 -We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.
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.**
376 376  
377 ----
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
378 378  
379 -## Terminology
380 -| Term | Meaning |
381 -|------|---------|
382 -| **Old Repository** | The existing HTTP/HTTPS ChartMuseum repository. |
383 -| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). |
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`).
384 384  
385 ----
360 +##__**Why This Migration Is Required:**__##
386 386  
387 -## Why This Migration Is Required
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**.
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**.##
391 391  
392 ----
366 +## Migration Steps:##
393 393  
394 -## Migration Steps
395 -
396 -### 1. Create the New OCI Repository in Rancher
397 -1. Go to **Apps → Repositories**.
398 -2. Add a new repository of type **OCI**.
399 -3. Name it exactly like your old repo name (e.g. `<chart-repo-name>`).
400 -4. Point it to the new OCI endpoint.
401 -
402 ----
403 -
404 -### 2. Disable the Old ChartMuseum Repository Temporarily
405 -This step ensures that Rancher resolves charts from the new OCI repo.
406 -
407 -1. Go to **Apps → Repositories**.
408 -2. Disable the old HTTP(S)-based repository.
409 -3. Keep it disabled until the migration is done.
410 -
411 ----
412 -
413 -### 3. Update Existing Applications to Use the New OCI Repo
414 -Applications deployed with the old repository still contain the old repo name in their metadata.
415 -You must upgrade them once to transition.
416 -
417 -1. Go to **Apps → Installed Apps**.
418 -2. Open the application that was deployed using the old repo.
419 -3. Click **Upgrade**.
420 -4. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
421 -5. Choose the chart version you want to deploy (same or newer).
422 -6. Click **Upgrade**.
423 -
424 -After this upgrade:
425 -- Your application is now linked to the **new OCI repository**.
426 -- Rancher will show upgrade notifications only for versions available in the new repo.
427 -
428 ----
429 -
430 -### 4. Re-enable the Old Repository (Optional)
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) ##
431 431  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
432 432  
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.
393 +##If you want to move an app back to the old repository:##
434 434  
435 ----
436 -
437 -## Reverting the Migration (If Needed)
438 -If you want to move an app back to the old repository:
439 439  1. Temporarily disable the new OCI repo.
440 -2. Enable the old ChartMuseum repo.
441 -3. Open the application → **Upgrade**.
442 -4. Select the chart from the old repo.
443 -5. Save.
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.
444 444  
445 445  This will reconnect the app to the old repository.
446 446  
447 ----
448 -
449 -## Summary
450 -- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
451 -- After upgrade, apps no longer track versions from the old repository.
452 -- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.
453 -
454 ----
455 -
456 -If you want, I can also generate:
457 -- a shorter version (1-pager),
458 -- a diagram,
459 -- a Rancher UI screenshot guide,
460 -- or a version tailored for your team’s internal wiki.
461 -
462 -
463 463  = Automated deployments with Jenkins =
464 464  
465 465  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