Project

General

Profile

Actions

action #179750

closed

[BCI] Plan testing of Harbor

Added by ph03nix 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2025-04-01
Due date:
% Done:

100%

Estimated time:
Tags:

Description

Discussed in BCI meeting on 01.04.2025. We need more information about the test subjects.

Dirk, can you post here a link to the containers in question and the available helm charts as a starting point for the research?


Related issues 1 (1 open0 closed)

Related to Containers and images - action #181238: [BCI] Implement test for HarborIn Progresshilchev2025-04-22

Actions
Actions #1

Updated by dirkmueller 2 months ago · Edited

slack: #proj-private-registry
PM: Hernan Schmidt
PrjM: Nadja Walter

IBS-cr: SUSE:SLE-15-SP6:Update:Products:PrivateRegistry
IBS-totest: SUSE:SLE-15-SP6:Update:Products:PrivateRegistry:ToTest
IBS-release: SUSE:Containers:PrivateRegistry:15-SP6

Actions #2

Updated by ph03nix about 2 months ago

In https://build.suse.de/project/show/SUSE:SLE-15-SP6:Update:Products:PrivateRegistry I see the following packages:

  • go-swagger
  • harbor-core-container
  • harbor-db-container
  • harbor-distribution
  • harbor-entrypoint
  • harbor-exporter-container
  • harbor-jobservice-container
  • harbor-nginx-container
  • harbor-portal-container
  • harbor-registry-container
  • harbor-registryctl-container
  • harbor-scanner-trivy
  • harbor-trivy-adapter-container
  • harbor-valkey-container
  • harbor212
  • private-registry-helm
  • trivy
Actions #3

Updated by ph03nix about 2 months ago

Project page: https://goharbor.io/

Actions #5

Updated by ph03nix about 2 months ago · Edited

Test plan suggestion

Based on the available artifacts I propose the following test coverage based on two test scenarios:

  1. Image testing, based on released helm chart
  2. Helm chart testing, based on released images

Testing needs to happen in a new openQA module, which deploys the application using helm. Both test scenarios should use the same openQA tests, if possible.

We need to test each image before it is released. For that we should use the already released helm chart and the image under test.

We also need to test helm chart updates. For that we use the new helm chart with the already released images.

Open questions

  • Can the images and the helm chart be tested independently from each other or are the depending on each other?
  • Will image updates be released first and then helm chart updates or together?
Actions #6

Updated by ph03nix about 2 months ago

ph03nix wrote in #note-5:

Open questions

  • Can the images and the helm chart be tested independently from each other or are the depending on each other?
  • Will image updates be released first and then helm chart updates or together?

See https://suse.slack.com/archives/C02AF8LALDA/p1744884231755939

the answers are:

  • containers first, chart second
  • release is independent. containers first, chart second
Actions #7

Updated by ph03nix about 1 month ago

Actions #8

Updated by ph03nix about 1 month ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Implementation ticket: #181238

Actions

Also available in: Atom PDF