Changes for page Rancher 2
Last modified by Diana Strebkova on 2025/12/12 14:23
From version 11.2
edited by Diana Strebkova
on 2025/12/12 12:09
on 2025/12/12 12:09
Change comment:
There is no comment for this version
To version 10.10
edited by Diana Strebkova
on 2025/12/12 11:55
on 2025/12/12 11:55
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -281,6 +281,7 @@ 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" %) 284 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 ... ... @@ -315,7 +315,7 @@ 315 315 ==== Target: OCI Repository ==== 316 316 317 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.//** 319 +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}} 320 320 321 321 (% class="p1" %) ... ... @@ -345,122 +345,25 @@ 345 345 |=((( 346 346 Name 347 347 )))|((( 348 - sdcloud-sdportal349 +devopsaas-jenkins-auto-agent 349 349 ))) 350 350 |=((( 351 351 Description 352 352 )))|((( 353 - Sdportal charts ofsdcloudoject354 +Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]] 354 354 ))) 355 355 |=((( 356 356 Index URL 357 357 )))|((( 358 -oci:~/~/registry.sdc.t-systems.net/ sdcloud-helm/sdportal359 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example: 359 359 361 +oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib 362 + 360 360 {{info}} 361 - Now weshouldtarget achartrepodirectly,notthewholeproject. Inyouneedtoreferencethewholeprojectwitha lot ofrepos,please contact supportto findapossible solution.364 +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. 362 362 {{/info}} 363 363 ))) 364 364 365 -=== Migrating chart repositories in rancher to new OCI Repository format === 366 - 367 -(% class="wikigeneratedid" %) 368 - 369 -##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)**.## 370 - 371 -To ensure a smooth transition, we recomment should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase. 372 - 373 -We will make your charts available in the corresponding new `<pkey>-helm` OCI projects. 374 - 375 ------ 376 - 377 -## Terminology## 378 - 379 -| Term | Meaning | 380 -| |-| 381 -| **Old Repository** | The existing HTTP/HTTPS ChartMuseum repository. | 382 -| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). | 383 - 384 ------ 385 - 386 -## Why This Migration Is Required 387 -- ChartMuseum is deprecated and will be removed. 388 -- Applications deployed from old repos keep a reference to that repo inside their labels. 389 -- Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions**.## 390 - 391 ------ 392 - 393 -## Migration Steps## 394 - 395 -### 1. Create the New OCI Repository in Rancher## 396 - 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) 431 -If you still need the old repo for other apps, re-enable it after the migration steps above.## 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. 434 - 435 ------ 436 - 437 -## Reverting the Migration (If Needed) 438 -If you want to move an app back to the old repository:## 439 - 440 -1. Temporarily disable the new OCI repo. 441 -2. Enable the old ChartMuseum repo. 442 -3. Open the application → **Upgrade**. 443 -4. Select the chart from the old repo. 444 -5. Save. 445 - 446 -This will reconnect the app to the old repository. 447 - 448 ------ 449 - 450 -## Summary 451 -- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo. 452 -- After upgrade, apps no longer track versions from the old repository. 453 -- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.## 454 - 455 ------ 456 - 457 -If you want, I can also generate: 458 -- a shorter version (1-pager), 459 -- a diagram, 460 -- a Rancher UI screenshot guide, 461 -- or a version tailored for your team’s internal wiki. 462 - 463 - 464 464 = Automated deployments with Jenkins = 465 465 466 466 In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.