Changes for page Rancher 2

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

From 10.10 to 10.9 From 11.2 to 11.1

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 10.10

edited by Diana Strebkova
on 2025/12/12 11:55

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -316,7 +316,7 @@
  ==== 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.//** If you have a real need to add the whole project, please contact support for finding a possible solution.**//
++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" %)
@@ -346,120 +346,25 @@
  |=(((
  Name
  )))|(((
--sdcloud-sdportal
++devopsaas-jenkins-auto-agent
  )))
  |=(((
  Description
  )))|(((
--Sdportal charts of sdcloud project
++Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
  )))
  |=(((
  Index URL
  )))|(((
--oci:~/~/registry.sdc.t-systems.net/sdcloud-helm/sdportal
++oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/**<chartname>**, for example:
++oci:~/~/registry.sdc.t-systems.net/devopsaas-helm/jenkins-lib
++
  {{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.
++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}}
  )))
--=== Migrating chart repositories in rancher to new OCI Repository format ===
--
--# Migration Guide: ChartMuseum → OCI-based Chart Repositories in Rancher
--
--## Overview
--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**.
--
--To ensure a smooth transition, each project 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.

Changes for page Rancher 2

Summary

Details

DevOps-as-a-Service

Navigation