Skip to Content

Changes for page Rancher 2

Last modified by Diana Strebkova on 2025/12/12 14:23
From version 10.3
edited by Diana Strebkova
on 2025/12/12 11:43
Change comment: There is no comment for this version
To version 1.2
edited by Diana Strebkova
on 2025/12/08 15:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -158,8 +158,8 @@
158 158  
159 159  == Add public helm chart ==
160 160  
161 -{{warning width="70" title="Chartmuseum Deprecation"}}
162 -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.
161 +{{warning}}
162 +Chartmuseum is deprecated in new Harbor version, we are migration all helm chart to oci cim
163 163  {{/warning}}
164 164  
165 165  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.
... ... @@ -177,13 +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 187  (% class="p1" %)
188 188  In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
189 189  
... ... @@ -218,44 +218,6 @@
218 218  
219 219  [[image:Screenshot 2024-07-03 at 15.13.55.png||data-xwiki-image-style-border="true" height="149" width="785"]]
220 220  
221 -==== Target: OCI Repository ====
222 -
223 -To add public oci-repository, navigate to repository create button and click it. For target, use OCI Repository like shown below:
224 -
225 -[[image:1765207154466-828.png||height="298" width="821"]]
226 -
227 -In the "Repository: Create" dialog, simply fill in the following fields. Authentication is not required.
228 -
229 -(% class="wrapped" %)
230 -|=(((
231 -Field
232 -)))|=(((
233 -Value
234 -)))
235 -|=(((
236 -Name
237 -)))|(((
238 -devopsaas-jenkins-auto-agent
239 -)))
240 -|=(((
241 -Description
242 -)))|(((
243 -Public Helm charts as documented at [[https:~~/~~/docs.devops.t-systems.net>>url:https://docs.devops.t-systems.net||shape="rect"]]
244 -)))
245 -|=(((
246 -Index URL
247 -)))|(((
248 -oci:[[~~/~~/registry.sdc.t-systems.net/chartrepo/devopsaas-helm/>>url:https://registry.sdc.t-systems.net/chartrepo/devopsaas/||shape="rect"]]chartname, for example:
249 -
250 -oci:~/~/registry.sdc.t-systems.net/chartrepo/devopsaas-helm/chartname
251 -
252 -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]]
253 -)))
254 -
255 -{{info}}
256 -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.
257 -{{/info}}
258 -
259 259  === Deploy Helm charts ===
260 260  
261 261  Now go to Apps>Charts and filter if necessary for the devops-as-a-service Helm chart repository. Like shown below, a list of available charts is displayed. Simply click on one of the tiles to deploy them to your cluster.
... ... @@ -284,18 +284,9 @@
284 284  (% class="p1" %)
285 285  Create a new Repository by pressing the Create button.
286 286  
287 -(% id="HTarget:http28s29URL-1" class="p1" %)
288 -==== [[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"]] ====
289 -
290 -(% id="HTarget:http28s29URL-1" class="p1" %)
291 -==== Target: http(s) URL ====
292 -
293 -{{warning title="Chartmuseum Deprecation"}}
294 -Chartmuseum in Harbor is deprecated, meaning we won't be able to add repositories to Rancher that way anymore. Instead use Target: OCI repository.
295 -{{/warning}}
296 -
297 297  (% class="p1" %)
298 -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.
243 +[[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"]]
244 +\\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.
299 299  Choose http(s) URL to an index generated by Helm and provide the Index URL ##https:~/~/registry-<domain>.devops.t-systems.net/chartrepo/<project>/##
300 300  
301 301  (% class="p1" %)
... ... @@ -308,28 +308,7 @@
308 308  (% class="p1" %)
309 309  Click Create.
310 310  
311 -(% id="HTarget:OCIRepository-1" class="p1" %)
312 -==== Target: OCI Repository ====
313 313  
314 -{{info}}
315 -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.
316 -{{/info}}
317 -
318 -(% class="p1" %)
319 -Choose OCI repository in Target and for url, use  ##oci:~/~/registry-<domain>.devops.t-systems.net/<project>-helm/<chatname>##
320 -
321 -(% class="p1" %)
322 -Replace ##<domain>## , ##<project>##  and ##<chatname> ##as necessary to match your set-up.
323 -
324 -(% class="p1" %)
325 -For Authentication, select "Create a HTTP Basic Auth Secret" and provide the Username and Password of the Harbor robot account from the previous section.
326 -
327 -(% class="wikigeneratedid" %)
328 -[[image:1765208347952-345.36.18.png||height="449" width="849"]]
329 -
330 -(% class="wikigeneratedid" %)
331 -Click Create.
332 -
333 333  = Automated deployments with Jenkins =
334 334  
335 335  In this section, we describe(% style="color:#172b4d" %) how to set-up **automated builds, tests and deployments** for Jenkins.
1765206888644-487.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -142.4 KB
Content
1765207032873-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -142.1 KB
Content
1765207154466-828.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -143.6 KB
Content
1765208347952-345.36.18.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.dianastrebkovat-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -199.3 KB
Content
© 2018-2025 T-Systems International GmbH