Skip to content

chore(berserker): Use stackrox-io repo berserker image#19953

Open
JoukoVirtanen wants to merge 4 commits intomasterfrom
jv-use-stackrox-io-berserker
Open

chore(berserker): Use stackrox-io repo berserker image#19953
JoukoVirtanen wants to merge 4 commits intomasterfrom
jv-use-stackrox-io-berserker

Conversation

@JoukoVirtanen
Copy link
Copy Markdown
Contributor

@JoukoVirtanen JoukoVirtanen commented Apr 12, 2026 •
edited
Loading

Description

Currently the berserker images used by the long running clusters are in the private rhacs-eng image repository. This requires setting up an image pull secret, which is a complication. To simplify things, switch to using the public images in the stackrox-io repository.

User-facing documentation

Testing and quality

  • the change is production ready: the change is GA, or otherwise the functionality is gated by a feature flag
  • CI results are inspected

Automated testing

  • added unit tests
  • added e2e tests
  • added regression tests
  • added compatibility tests
  • modified existing tests

How I validated my change

Created jv-use-stackrox-io-berserker branches in the stackrox/actions and stackrox/test-gh-actions repositories.

Ran the following steps

Went to https://github.com/stackrox/test-gh-actions/actions/workflows/create-clusters.yml
Clicked on "Run workflow"
Selected jv-use-stackrox-io-berserker as the branch
Selected 4.11.x-628-g0d69df3da2 as the image which corresponds to this branch
Selected Create a long-running cluster on RC1
Clicked on "Run workflow"

The workflow succeeded.
Downloaded the artifacts for the cluster with real workload. Checked the namespaces in the cluster.

$ kc get ns
NAME                          STATUS   AGE
berserker-1                   Active   19m
berserker-2                   Active   10s
berserker-3                   Active   6s
berserker-4                   Active   4s
berserker-5                   Active   1s
default                       Active   122m
gke-managed-cim               Active   120m
gke-managed-system            Active   120m
gke-managed-volumepopulator   Active   120m
gmp-public                    Active   120m
gmp-system                    Active   120m
kube-burner                   Active   20m
kube-node-lease               Active   122m
kube-public                   Active   122m
kube-system                   Active   122m
stackrox                      Active   22m

Checked the berserker pods in the namespaces. Here is one of the namespaces

$ kc -n berserker-1 get pod
NAME                      READY   STATUS    RESTARTS   AGE
connection-load-1-5hxv9   1/1     Running   0          2m41s
connection-load-1-8r69j   1/1     Running   0          2m40s
connection-load-1-jgkzd   1/1     Running   0          2m42s
connection-load-1-nqhk4   1/1     Running   0          2m41s
connection-load-1-sclxr   1/1     Running   0          2m41s
connection-load-2-b2dcs   1/1     Running   0          2m33s
connection-load-2-bkxhr   1/1     Running   0          2m35s
connection-load-2-kzkcj   1/1     Running   0          2m32s
connection-load-2-mtq9z   1/1     Running   0          2m32s
connection-load-2-xnsfj   1/1     Running   0          2m33s
connection-load-3-2v2jp   1/1     Running   0          2m35s
connection-load-3-7wzpp   1/1     Running   0          2m36s
connection-load-3-gthqr   1/1     Running   0          2m37s
connection-load-3-k44ls   1/1     Running   0          2m35s
connection-load-3-tttbh   1/1     Running   0          2m36s
connection-load-4-4mslq   1/1     Running   0          2m33s
connection-load-4-95xdg   1/1     Running   0          2m33s
connection-load-4-gsr4l   1/1     Running   0          2m35s
connection-load-4-hlx9l   1/1     Running   0          2m35s
connection-load-4-kl655   1/1     Running   0          2m35s
connection-load-5-58vmj   1/1     Running   0          2m33s
connection-load-5-7s22z   1/1     Running   0          2m33s
connection-load-5-b9ksj   1/1     Running   0          2m35s
connection-load-5-nth98   1/1     Running   0          2m34s
connection-load-5-ss4cr   1/1     Running   0          2m34s
connection-load-6-29zp9   1/1     Running   0          2m36s
connection-load-6-5gpv4   1/1     Running   0          2m36s
connection-load-6-bwb2m   1/1     Running   0          2m37s
connection-load-6-cf7r9   1/1     Running   0          2m37s
connection-load-6-crkcf   1/1     Running   0          2m40s
endpoint-load-1-6fwjr     1/1     Running   0          2m42s
endpoint-load-1-rx9m8     1/1     Running   0          2m41s
endpoint-load-1-s7nbf     1/1     Running   0          2m42s
endpoint-load-1-x24hs     1/1     Running   0          2m41s
endpoint-load-1-z9tjk     1/1     Running   0          2m42s
endpoint-load-2-88fqj     1/1     Running   0          2m41s
endpoint-load-2-8hxdk     1/1     Running   0          2m42s
endpoint-load-2-cgd6m     1/1     Running   0          2m42s
endpoint-load-2-kjv67     1/1     Running   0          2m41s
endpoint-load-2-rbvk2     1/1     Running   0          2m42s
endpoint-load-3-788xb     1/1     Running   0          2m37s
endpoint-load-3-hrlrq     1/1     Running   0          2m38s
endpoint-load-3-p2mh6     1/1     Running   0          2m36s
endpoint-load-3-v7mzq     1/1     Running   0          2m38s
endpoint-load-3-w56z7     1/1     Running   0          2m37s
endpoint-load-4-4lr4r     1/1     Running   0          2m38s
endpoint-load-4-8lp7d     1/1     Running   0          2m37s
endpoint-load-4-dgdjc     1/1     Running   0          2m36s
endpoint-load-4-gmqh8     1/1     Running   0          2m40s
endpoint-load-4-h59jr     1/1     Running   0          2m36s
endpoint-load-5-9fxp2     1/1     Running   0          2m40s
endpoint-load-5-dz6g8     1/1     Running   0          2m42s
endpoint-load-5-gxw8z     1/1     Running   0          2m42s
endpoint-load-5-kndzl     1/1     Running   0          2m41s
endpoint-load-5-lgxcl     1/1     Running   0          2m42s
endpoint-load-6-4rcs7     1/1     Running   0          2m39s
endpoint-load-6-bpgch     1/1     Running   0          2m40s
endpoint-load-6-lcv5z     1/1     Running   0          2m39s
endpoint-load-6-mf8rj     1/1     Running   0          2m38s
endpoint-load-6-zwqsw     1/1     Running   0          2m37s
process-load-1-2ztvq      1/1     Running   0          2m42s
process-load-1-6fq8n      1/1     Running   0          2m41s
process-load-1-l8s2d      1/1     Running   0          2m42s
process-load-1-nk7j6      1/1     Running   0          2m41s
process-load-1-pt7b8      1/1     Running   0          2m43s
process-load-2-2r54h      1/1     Running   0          2m43s
process-load-2-2zzth      1/1     Running   0          2m44s
process-load-2-5d7rb      1/1     Running   0          2m43s
process-load-2-dn5m9      1/1     Running   0          2m44s
process-load-2-vlgqp      1/1     Running   0          2m44s
process-load-3-685wt      1/1     Running   0          2m44s
process-load-3-8wpb2      1/1     Running   0          2m44s
process-load-3-9zwxx      1/1     Running   0          2m43s
process-load-3-gbsjz      1/1     Running   0          2m43s
process-load-3-j9w22      1/1     Running   0          2m44s
process-load-4-4gbtf      1/1     Running   0          2m44s
process-load-4-927gx      1/1     Running   0          2m44s
process-load-4-hh5g8      1/1     Running   0          2m44s
process-load-4-t2vjr      1/1     Running   0          2m43s
process-load-4-z4ckr      1/1     Running   0          2m43s
process-load-5-4rbjp      1/1     Running   0          2m43s
process-load-5-dkd8z      1/1     Running   0          2m44s
process-load-5-hndzn      1/1     Running   0          2m44s
process-load-5-s4tcv      1/1     Running   0          2m44s
process-load-5-xgv8v      1/1     Running   0          2m43s
process-load-6-5bdgm      1/1     Running   0          2m44s
process-load-6-75pmk      1/1     Running   0          2m44s
process-load-6-ccwpw      1/1     Running   0          2m43s
process-load-6-fb8bn      1/1     Running   0          2m44s
process-load-6-k6qk6      1/1     Running   0          2m43s

Checked the image in one of the pods

$ kc -n berserker-1 describe pod connection-load-1-5hxv9 | grep image
  Normal   Pulled       21m   kubelet            Container image "quay.io/stackrox-io/berserker:network-1.0-85-g1b7ab034aa" already present on machine

@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 12, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 12, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.56%. Comparing base (a1fe1e9) to head (0d69df3).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files 
@@           Coverage Diff           @@
##           master   #19953   +/-   ##
=======================================
  Coverage   49.56%   49.56%           
=======================================
  Files        2764     2764           
  Lines      208357   208357           
=======================================
  Hits       103269   103269           
  Misses      97436    97436           
  Partials     7652     7652
Flag Coverage Δ
go-unit-tests 49.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 12, 2026 •
edited
Loading

🚀 Build Images Ready

Images are ready for commit 0d69df3. To use with deploy scripts:

export MAIN_IMAGE_TAG=4.11.x-628-g0d69df3da2

@JoukoVirtanen JoukoVirtanen marked this pull request as ready for review April 13, 2026 04:08
@JoukoVirtanen JoukoVirtanen changed the title Jv use stackrox io berserker chore(berserker): Use stackrox-io repo berserker image Apr 13, 2026
@JoukoVirtanen JoukoVirtanen requested a review from mtodor April 13, 2026 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mtodor mtodor Awaiting requested review from mtodor

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@JoukoVirtanen