Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23

From 9.1 to 10.1 From 11.2 to 11.3

From version 10.1

edited by Diana Strebkova
on 2025/12/08 15:45

Change comment: There is no comment for this version

To version 11.2

edited by Diana Strebkova
on 2025/12/12 12:09

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -159,7 +159,7 @@
  == Add public helm chart ==
  {{warning width="70" title="Chartmuseum Deprecation"}}
--Chartmuseum is deprecated in new Harbor versions, we are migrating all helm charts to oci-compatible repositories in Harbor! New approach to add chart repositories in rancher.
++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.
  {{/warning}}
  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.
@@ -220,7 +220,7 @@
  ==== Target: OCI Repository ====
--To add public oci-repository, navigate to repository create button and click it.
++To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
  [[image:1765207154466-828.png||height="298" width="821"]]
@@ -245,13 +245,17 @@
  |=(((
  Index URL
  )))|(((
--oci:[[~~/~~/registry.sdc.t-systems.net/chartrepo/devopsaas-helm/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]]chartname, for example:
++oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
--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]]
++oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
++
++{{info}}
++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.
++{{/info}}
  )))
  {{info}}
--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.
++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.**//
  {{/info}}
  === Deploy Helm charts ===
@@ -264,7 +264,6 @@
  == Add private chart repository ==
--
  === Create a robot account in Harbor ===
  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,6 +277,8 @@
  (% class="p1" %)
  In Rancher UI, switch to the intended cluster and go to Apps/Repositories using the left side menu.
++
++
  [[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"]]
  (% class="p1" %)
@@ -285,11 +285,11 @@
  (% id="HTarget:http28s29URL-1" class="p1" %)
  ==== [[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"]] ====
--(% class="p1" %)
++(% id="HTarget:http28s29URL-1" class="p1" %)
  ==== Target: http(s) URL ====
  {{warning title="Chartmuseum Deprecation"}}
--Chartmuseum in Harbor is deprecated, meaning we won't be able to add repositories to Rancher that way anymore. Instead use Target: OCI repository.
++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.
  {{/warning}}
  (% class="p1" %)
@@ -306,18 +306,20 @@
  (% class="p1" %)
  Click Create.
--(% class="p1" %)
++(% id="HTarget:OCIRepository-1" class="p1" %)
  ==== Target: OCI Repository ====
  {{info}}
--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.
++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.**//
  {{/info}}
  (% class="p1" %)
--Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chatname>##
++Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chartname>##
--(% class="p1" %)
--Replace ##<domain>## , ##<project>##  and ##<chatname> ##as necessary to match your set-up.
++(% class="box" %)
++(((
++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.
++)))
  (% class="p1" %)
  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,132 @@
  (% class="wikigeneratedid" %)
  Click Create.
++
++(% class="wrapped" %)
++|=(((
++Field
++)))|=(((
++Value
++)))
++|=(((
++Name
++)))|(((
++sdcloud-sdportal
++)))
++|=(((
++Description
++)))|(((
++Sdportal charts of sdcloud project
++)))
++|=(((
++Index URL
++)))|(((
++oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
++
++{{info}}
++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.
++{{/info}}
++)))
++
++=== Migrating chart repositories in rancher to new OCI Repository format ===
++
++(% class="wikigeneratedid" %)
++
++##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)**.##
++
++To ensure a smooth transition, we recomment should **add an OCI-based repository alongside the existing ChartMuseum repository** during the migration phase.
++
++We will make your charts available in the corresponding new `<pkey>-helm` OCI projects.
++
++-----
++
++## Terminology##
++
++| Term | Meaning |
++| |-|
++| **Old Repository** | The existing HTTP/HTTPS ChartMuseum repository. |
++| **New Repository** | The new OCI-based Helm chart repository created for your project (e.g. `<chart-repo-name>` in `<pkey>-helm`). |
++
++-----
++
++## Why This Migration Is Required
++- ChartMuseum is deprecated and will be removed.
++- Applications deployed from old repos keep a reference to that repo inside their labels.
++- Without updating the application to point to the new OCI repo, **Rancher will not detect new chart versions**.##
++
++-----
++
++## Migration Steps##
++
++### 1. Create the New OCI Repository in Rancher##
++
++1. Go to **Apps → Repositories**.
++2. Add a new repository of type **OCI**.
++3. Name it exactly like your old repo name (e.g. `<chart-repo-name>`).
++4. Point it to the new OCI endpoint.
++
++-----
++
++### 2. Disable the Old ChartMuseum Repository Temporarily
++This step ensures that Rancher resolves charts from the new OCI repo.##
++
++1. Go to **Apps → Repositories**.
++2. Disable the old HTTP(S)-based repository.
++3. Keep it disabled until the migration is done.
++
++-----
++
++### 3. Update Existing Applications to Use the New OCI Repo
++Applications deployed with the old repository still contain the old repo name in their metadata.
++You must upgrade them once to transition.##
++
++1. Go to **Apps → Installed Apps**.
++2. Open the application that was deployed using the old repo.
++3. Click **Upgrade**.
++4. In the list of available chart repositories (scroll to the bottom), select the **new OCI repository**.
++5. Choose the chart version you want to deploy (same or newer).
++6. Click **Upgrade**.
++
++After this upgrade:
++- Your application is now linked to the **new OCI repository**.
++- Rancher will show upgrade notifications only for versions available in the new repo.
++
++-----
++
++### 4. Re-enable the Old Repository (Optional)
++If you still need the old repo for other apps, re-enable it after the migration steps above.##
++
++> 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.
++
++-----
++
++## Reverting the Migration (If Needed)
++If you want to move an app back to the old repository:##
++
++1. Temporarily disable the new OCI repo.
++2. Enable the old ChartMuseum repo.
++3. Open the application → **Upgrade**.
++4. Select the chart from the old repo.
++5. Save.
++
++This will reconnect the app to the old repository.
++
++-----
++
++## Summary
++- Add new OCI repo → disable old repo → upgrade apps → reconnect to OCI repo.
++- After upgrade, apps no longer track versions from the old repository.
++- Old repository will stop functioning after ChartMuseum shutdown, so migration is required.##
++
++-----
++
++If you want, I can also generate:
++- a shorter version (1-pager),
++- a diagram,
++- a Rancher UI screenshot guide,
++- or a version tailored for your team’s internal wiki.
++
++
  = Automated deployments with Jenkins =
  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.