-
Notifications
You must be signed in to change notification settings - Fork 9
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
use registry.access.redhat.com/ubi8-minimal for multi-arch support #7
Conversation
@yselkowitz: GitHub didn't allow me to request PR reviews from the following users: gabemontero. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
/cc @gabemontero |
@yselkowitz: GitHub didn't allow me to request PR reviews from the following users: gabemontero. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
@yselkowitz I'd rather pull down the docker.io busybox, docker tag it, and push it to quay.io/redhat-developer to avoid docker.io throttling @sbose78 can help us with creating the landing spot in quay.io/redhat-developer @bparees @adambkaplan FYI |
How often are you building this that their rate limiting would be an issue? |
even if this is a special case and does not get rebuilt often, throttling has been enough of a pain point I don't want this getting caught up in some sort of "docker.io" scan or something ... call it "good PR" I'll ping @sbose78 this afternoon after all my meetings if he dies not see this mention in the interim |
could we (feasibly) switch these to e.g. ubi8-minimal instead? |
I'm willing to try that yes. It would involve creating the image and then modifying openshift/origin e2e's and running them against a personal cluster to confirm it works. |
Well, to say I'm willing, I mean I'm willing for someone to try it :-) It would minimally be next week before I could get to it |
Multi-arch images for testing, with docker.io/busybox: quay.io/multi-arch/test-build-roots2i:latest With ubi8-minimal: quay.io/multi-arch/test-build-roots2i:ubi8 |
As a possible alternative, do we own this: quay.io/openshifttest/busybox:multiarch |
I can help! |
@yselkowitz just to be sure, when you say "multi arch image", you mean you can use Assuming so, the process here is as follows: You very well may have already done this, but the hits under the test/extended from one's https://github.com/openshift/origin clone are, where one would change from quay.io/redhat-developer to quay.io/multi-arch:
you then make clean / make build to get a new
Assuming things work, we merge this, and someone starts on the openshift/origin PR for those above hits. the util image hits are fun. That is all part of Clayton's initiative to make e2e's fully "disconnected" where are all images are accessed from mirrors set up in CI. The process for all that is documented at https://github.com/openshift/origin/tree/master/test/extended/util/image Ultimately, you need to work with Clayton directly to get him to push a version of these images to registry.ci.openshift.org/ocp |
I've also opened https://issues.redhat.com/browse/BUILD-250 to track getting this done by someone on the build api team if we do not get to this in "less official" fashion so to speak |
So per openshift/origin#26149 (comment) @yselkowitz I'm lending a quick assist to @alicerum and trying out "quay.io/multi-arch/test-build-roots2i:ubi8" on its own now. I'll report back with results. Assuming things are good, let's switch to ubi8-minimal in this PR and merge it. That will facilitate the BUILD-250 work she is doing. We can consider ubi8-micro at a later date. |
Or if you'd rather we craft our own PR @yselkowitz to replace what you have here, we can do that too. Thanks. |
thanks @yselkowitz /retitle use registry.access.redhat.com/ubi8-minimal for multi-arch support |
fyi passed: (45.7s) 2021-05-11T22:54:39 "[sig-builds][Feature:Builds] s2i build with a root user image should create a root build and pass with a privileged SCC [Skipped:Disconnected] [Suite:openshift/conformance/parallel]" when I tried the multi-arch image locally |
also passed in my test PR and given the only minor diff between roots2i and simples2i @yselkowitz @alicerum @adambkaplan I think we can merge this /lgtm |
@gabemontero: changing LGTM is restricted to collaborators 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. |
ok @bparees or @adambkaplan will have to merge this |
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
@adambkaplan: changing LGTM is restricted to collaborators 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. |
fyi @gabemontero you are also listed as an approver in the OWNERS file, and should be able to approve/lgtm |
yep - spoke with dptp team, will be setting that up today. |
seems like the prow config for this repo is not correct. |
/lgtm |
@adambkaplan since this repo impacts e2e tests for the org(right?), merges to this repo should require e2e tests to pass. |
Correct - we should have e2e-* and e2e-*-build |
CI fixes for this repo: openshift/release#18523 |
Per #7 (comment) I ran build e2e using the manually built image @yselkowitz pushed to |
also the way the imagestream tagging and mirroring works these changes won't get picked up until we change openshift/origin to pick them up the roots2i tests works off of registry.ci.openshift.org/ocp/4.7:test-build-roots2i and its mapping to the associated mirrored image from quay.io/openshift/community-e2e-images This PR and openshift/release#18523 ultimately update registry.ci.openshift.org/ocp/4.8:test-build-roots2i It will be a 2 step process to change the e2e in https://github.com/openshift/origin/pull/26149/files to work off registry.ci.openshift.org/ocp/4.8:test-build-roots2i and a new mirrored mapping to quay.io/openshift/community-e2e-images So we merge openshift/release#18523 and then this one. The validate things in openshift/origin#26149 without disrupting other PRs or periodics, as we have not changed registry.ci.openshift.org/ocp/4.7:test-build-roots2i and its mapping to the associated mirrored image from quay.io/openshift/community-e2e-images (I'm re-learning the complicated https://github.com/openshift/origin/tree/master/test/extended/util/image process and now have (re)established some level of understanding) |
OK openshift/release#18523 has merged. I think we need to close and reopen this to pick up the CI changes. Will try other stuff first. The rest below is another attempt to explain our use of https://github.com/openshift/origin/tree/master/test/extended/util/image in relation to the (current at least) lack of need to run the e2e's. Though they can catch unexpected refs to the test images, so I am not advocating removing its use with this repo. To reiterate what I mentioned in #7 (comment), changes to this repo on its own are not going to affect e2e-aws or e2e-aws-builds on its own, as the openshift/origin tests are currently constructed, since our tests use the 4.7 images, and master branch now points to 4.8. Moving forward, if the image ref in openshift/origin is aligned with whatever release master branch is pointing to, then the effect will still not immediate, if we follow the prior convention of mapping registry.ci.openshift.org/ocp/4.8:test-build* to images in quay.io/openshift/community-e2e-images, where we need CI admins to push to quay.io/openshift/community-e2e-images We only need these tests to run if we ever have direct registry.ci.openshift.org/ocp/4.8:test-build* refs in our tests. Though if we do, that will possibly break down when running in disconnected (at least I think) |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan, bparees, gabemontero, yselkowitz 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 |
/refresh |
OK have the tide indicator now. |
So after openshift/release#18523 merged we got registry.ci.openshift.org/ocp/4.8 test-build-simples2i bd5bc84df5ba 2 hours ago 392 MB I'll check it periodically between now and Monday to make sure that gets updated based on this PR merging. Assuming it does, the story will continue in openshift/origin#26149 where we update the e2e's and some someone from https://github.com/openshift/origin/blob/master/test/extended/util/image/OWNERS to mirror to Ultimately, per the "https://github.com/openshift/origin/blob/master/test/extended/util/image/README.md process" for lack of a better term, someone from https://github.com/openshift/origin/blob/master/test/extended/util/image/OWNERS will have to mirror the multi arch versions of these images to |
registry.ci update as a result of this PR occurred: registry.ci.openshift.org/ocp/4.8 test-build-simples2i 535d5b6dc170 About an hour ago 392 MB |
Unfortunately, quay.io/quay/busybox is single-arch.
/cc @gabemontero