Use OCP internal registry image for workload test pods - #58
Conversation
|
Warning Review limit reached
Next review available in: 29 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughIntroduces a shared default workload image constant and updates FAR, SBR, and SNR test parameters to reference it. SNR documentation now describes internal registry usage and support for connected or disconnected environments. ChangesWorkload image defaults
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Summary by QodoUse OpenShift internal registry image for test workload pods
AI Description
Diagram
High-Level Assessment
Files changed (3)
|
Code Review by Qodo
Context used✅ Compliance rules (platform):
13 rules 1.
|
06bb8a8 to
eddf0ae
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tests/snr-operator/internal/snrparams/const.go`:
- Line 127: Update PauseImage in the SNR test parameters to use a workload image
that provides /pause, or adjust the SNR workload setup in helpers.go so its
container command matches the selected image. Preserve successful workload pod
creation while keeping the existing SNR test configuration consistent.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 2081d984-aa22-493e-8cfd-f728c5316687
📒 Files selected for processing (5)
tests/far-operator/internal/farparams/const.gotests/internal/medik8sparams/const.gotests/sbr-operator/internal/sbrparams/const.gotests/snr-operator/README.mdtests/snr-operator/internal/snrparams/const.go
Replace external registry images (registry.access.redhat.com/ubi9/ubi-minimal, registry.k8s.io/pause:3.9) with image-registry.openshift-image-registry.svc:5000/ openshift/tools:latest across FAR, SBR, and SNR test params. The openshift/tools ImageStream is part of every OCP release payload and is guaranteed available on both connected and disconnected clusters. This follows the proven pattern used by openshift/origin, cluster-etcd-operator, external-dns-operator, and other OpenShift E2E test suites. Fixes FAR disconnected periodic job failure where 5 of 15 destructive tests failed with ImagePullBackOff because registry.access.redhat.com is unreachable from air-gapped clusters. Co-Authored-By: Claude <noreply@anthropic.com>
eddf0ae to
5b2b11b
Compare
|
/test 4.22-konflux-e2e-far-aws |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: razo7, ugreener The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
Replace external registry images (
registry.access.redhat.com/ubi9/ubi-minimal,registry.k8s.io/pause:3.9) with the OCP internal registryopenshift/toolsImageStream for test workload pods. This fixes disconnected (air-gapped) test failures and follows the proven pattern used by openshift/origin and other OCP E2E test suites.Changes
medik8sparams/const.go): AddedDefaultWorkloadImageto centralize the image string in one placefarparams/const.go):registry.access.redhat.com/ubi9/ubi-minimalreplaced withmedik8sparams.DefaultWorkloadImagesbrparams/const.go): same replacement for theWatchdogDebugImagedefaultsnrparams/const.go):registry.k8s.io/pause:3.9replaced withmedik8sparams.DefaultWorkloadImage; constant renamed fromPauseImagetoWorkloadTestImagehelpers.go): workload pod container changed frompause//pausetoworkload/sleep infinityThe
openshift/toolsImageStream is part of every OCP release payload and is automatically mirrored during cluster installation, making it available on both connected and disconnected clusters without any additional configuration.Prior art:
openshift/origin(test/extended/util/image/image.go),openshift/cluster-etcd-operator,openshift/external-dns-operator,openshift/aws-load-balancer-operatorall useimage-registry.openshift-image-registry.svc:5000/openshift/tools:latestfor test workload pods.