feat(benchmarks): make busybox image configurable via BUSYBOX_IMAGE env var#98
Open
k-wall wants to merge 1 commit into
Open
Conversation
…nv var The result collection pods use busybox to mount PVCs and copy files. Previously the image was hardcoded to docker.io busybox:1.37.0, which can hit Docker Hub rate limits in CI/testing environments. Added BUSYBOX_IMAGE environment variable to both scripts: - run-benchmark.sh: for OMB results collection pod - collect-results.sh: for JFR debug pod Default remains docker.io busybox:1.37.0 for backward compatibility. Users can now override to use alternative registries: BUSYBOX_IMAGE="quay.io/quay/busybox:latest" ./scripts/run-benchmark.sh ... This is particularly useful for: - OpenShift/Red Hat environments (quay.io has better connectivity) - CI environments hitting Docker Hub rate limits - Air-gapped environments with local mirrors Assisted-by: Claude Sonnet 4.5 <noreply@anthropic.com> Signed-off-by: Keith Wall <kwall@apache.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Makes the busybox image used by result collection pods configurable via the
BUSYBOX_IMAGEenvironment variable, allowing users to avoid Docker Hub rate limits by using alternative registries.Problem
During testing on OpenShift, result collection failed due to Docker Hub rate limiting:
The busybox image was hardcoded in two places:
run-benchmark.sh- OMB results reader pod (collectsresult.jsonfrom PVC)collect-results.sh- JFR debug pod (collects JFR recordings from PVC)This blocked test completion even though the actual benchmark ran successfully and metrics were collected.
Solution
Added
BUSYBOX_IMAGEenvironment variable to both scripts with sensible defaults:BUSYBOX_IMAGE="${BUSYBOX_IMAGE:-busybox:1.37.0@sha256:b3255e7dfbcd10cb367af0d409747d511aeb66dfac98cf30e97e87e4207dd76f}"Users can now override to use alternative registries:
Quay.io (Red Hat):
BUSYBOX_IMAGE="quay.io/quay/busybox:latest" ./scripts/run-benchmark.sh ...GHCR (GitHub Container Registry):
BUSYBOX_IMAGE="ghcr.io/dockerhub-mirror/busybox:latest" ./scripts/run-benchmark.sh ...Benefits
Documentation
Added to Environment section in both scripts' usage:
Testing
Verified on OpenShift with:
BUSYBOX_IMAGE="quay.io/quay/busybox:latest"- successfully avoided rate limits🤖 Generated with Claude Code