Skip to Content

Changes for page Rancher 2

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

Summary

Details

Page properties
Content
... ... @@ -177,6 +177,49 @@
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 +
180 180  To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
181 181  
182 182  [[image:1765207154466-828.png||height="298" width="821"]]
... ... @@ -204,11 +204,11 @@
204 204  )))|(((
205 205  oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
206 206  
207 -oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-auto-agent
250 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
208 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}}
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}}
212 212  )))
213 213  
214 214  {{info}}
... ... @@ -229,7 +229,7 @@
229 229  
230 230  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:
231 231  
232 -* Read Artifact
275 +* Read Helm Chart
233 233  * Pull Repository
234 234  
235 235  (% id="HCreateAppRepositoryinRancher-1" class="p1" %)
... ... @@ -238,17 +238,39 @@
238 238  (% class="p1" %)
239 239  In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
240 240  
284 +
241 241  [[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"]]
242 242  
243 243  (% class="p1" %)
244 244  Create a new Repository by pressing the Create button.
245 245  
246 -(% class="p1" id="HTarget:http28s29URL-1" %)
247 -[[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 +(% 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"]] ====
248 248  
249 249  (% id="HTarget:http28s29URL-1" class="p1" %)
250 -==== ====
294 +==== Target: http(s) URL ====
251 251  
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 +
252 252  {{info}}
253 253  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.**//
254 254  {{/info}}
... ... @@ -296,7 +296,7 @@
296 296  {{/info}}
297 297  )))
298 298  
299 -== Migrating chart repositories in rancher to new OCI Repository format ==
364 +=== Migrating chart repositories in rancher to new OCI Repository format ===
300 300  
301 301  (% class="box warningmessage" %)
302 302  (((
... ... @@ -303,34 +303,19 @@
303 303  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)**.
304 304  )))
305 305  
306 -(% class="box" %)
307 -(((
308 -**All ycharts 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.**
309 -)))
371 +There are 2 ways to "migrate" the repos:
310 310  
311 -There are two ways to migrate your repositories:
373 +1. You can do direct transition and edit already existing repository – choose //Target: OCI repository, //adapt the url as shown above (__repo name can't be changed__), then the installed apps will pick app the repo change automatically. The issue is that the OCI repository needs to target chart repos in the url, not the whole folder anymore.  That means if you previously deployed previously different apps using the old repo, for example "bitbucket" and "jira", now you can only target one repo, for example "bitbucket", other repos updates wont be working anymore and you will still need to create a new repo targeting each chartrepo.
374 +1. Or you can add new repositories one by one taking your time, while the old chartmuseum repo will still be functioning suring migraiton. For this, you can see the next described migration process.
375 +1. If you
312 312  
313 -1. ##Direct Transition (Editing the Existing Repository)##
314 -1*. Change the target to “OCI Repository”.
315 -1*. Update the URL as required (the repository name cannot be changed), check **Target: OCI Repository** documentation above
316 -1*. After saving, installed apps will automatically start using the updated repository.
317 -1*. (% class="box" %)
377 +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 +
379 +(% class="box" %)
318 318  (((
319 -Important limitation: OCI repositories must point directly to a single chart repository, not to a parent folder.
320 -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”).
321 -The other charts will no longer receive updates through this repo, and you will still need to create additional repositories for each individual chart.
381 +**We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.**
322 322  )))
323 -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:
324 -1*. Create a new OCI repository for each chart,
325 -1*. Keep the old ChartMuseum repo enabled during the migration,
326 -1*. Migrate applications gradually following the steps described here.
327 -1*. This avoids disruptions and allows controlled migration.
328 -
329 -1. //Special Case: Old Repo Targeting Multiple Chart Repos//
330 -If your existing repository targets multiple chart repositories and you need the new OCI setup to behave the same way, please **contact support.**
331 331  
332 -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
333 -
334 334  | Term | Meaning
335 335  | **Old Repository** | The existing HTTP/HTTPS Harbor ChartMuseum repository.
336 336  | **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`).
... ... @@ -346,7 +346,7 @@
346 346  1. ##Create the New OCI Repository in Rancher##
347 347  11. Go to **Apps → Repositories**.
348 348  11. Add a new repository of type **OCI**.
349 -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.**__
399 +11. Name it similarly to your old repo name (e.g. `<chart-repo-name>-oci`). You can't name it the same.
350 350  11. Point it to the new OCI endpoint.
351 351  1. ##Disable the Old ChartMuseum Repository Temporarily## 
352 352  ##This step ensures that Rancher resolves charts from the new OCI repo.##
... ... @@ -353,15 +353,12 @@
353 353  11. Go to **Apps → Repositories**.
354 354  11. Disable the old HTTP(S)-based repository.
355 355  11. Keep it disabled until the migration is done.
356 -[[image:1765548124989-482.59.06.png||height="152" width="485"]]
357 357  1. ##Update Existing Applications to Use the New OCI Repo##
358 358  Applications deployed with the old repository still contain the old repo name in their metadata. You must upgrade them once to transition.
359 359  11. Go to **Apps → Installed Apps**.
360 360  11. Open the application that was deployed using the old repo.
361 -11. Click **Edit/Upgrade**.
362 -[[image:1765548598644-830.png||height="138" width="811"]]
363 -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:
364 -[[image:1765548750604-334.png||height="293" width="308"]]
410 +11. Click **Upgrade**.
411 +11. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
365 365  11. Choose the chart version you want to deploy (same or newer).
366 366  11. Click **Upgrade**.
367 367  1. ##Re-enable the Old Repository (Optional) ##
... ... @@ -368,8 +368,11 @@
368 368  If you still need the old repo for other apps, re-enable it after the migration steps above.
369 369  **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
370 370  
371 -##If you want to move an app back to the old repository:##
418 +----
372 372  
420 +## Reverting the Migration (If Needed)
421 +If you want to move an app back to the old repository:##
422 +
373 373  1. Temporarily disable the new OCI repo.
374 374  1. Enable the old ChartMuseum repo.
375 375  1. Open the application → **Upgrade**.
... ... @@ -378,7 +378,8 @@
378 378  
379 379  This will reconnect the app to the old repository.
380 380  
381 -= Automated deployments with Jenkins =
431 +=
432 +Automated deployments with Jenkins =
382 382  
383 383  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
384 384  
1765548124989-482.59.06.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -64.4 KB
Content
1765548598644-830.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -153.4 KB
Content
1765548750604-334.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -103.0 KB
Content
© 2018-2026 T-Systems International GmbH