New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1920205: use secure local registry for e2e tests #552
Bug 1920205: use secure local registry for e2e tests #552
Conversation
Codecov Report
@@ Coverage Diff @@
## master #552 +/- ##
==========================================
+ Coverage 49.45% 49.49% +0.03%
==========================================
Files 90 91 +1
Lines 6317 6302 -15
==========================================
- Hits 3124 3119 -5
+ Misses 2497 2492 -5
+ Partials 696 691 -5
Continue to review full report at Codecov.
|
53a5893
to
e8c2e84
Compare
23afb54
to
c7051c4
Compare
The e2e tests are now passing -- all tests are being run with podman, docker, and containerd enabled. The goal of the PR was to enable testing against a local registry without make any substantial changes to the tests themselves. The only change to code was the potential for a data race that was uncovered in the containerd resolver.
Having this PR in the codebase will enable registry e2e tests to run on every commit and help ensure stability for large changes to the registry like in the declarative index proposal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Just a nit.
@exdx: This pull request references Bugzilla bug 1920205, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@exdx: This pull request references Bugzilla bug 1920205, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: Daniel Sover <dsover@redhat.com>
c7051c4
to
6e870ac
Compare
/approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a quick question.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dinhxuanvu, exdx, kevinrizza The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@exdx: All pull requests linked via external trackers have merged: Bugzilla bug 1920205 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/label qe-approved |
Description of the change:
Use local docker registry instead of quay.io for pushing images during the course of opm e2e tests
Motivation for the change:
The e2e tests are currently skipped on forks because the quay credentials cannot be securely provided to the fork. The e2e image has been made public and a local registry is spun up during the course of the test instead.
Reviewer Checklist
/docs