update README for registry.reg-aws migration #125
Comments
we have a job called so currently we have |
|
This will go away once brew pushes direct to Quay. This likely won't happen
for a while though.
Nothing changes currently.
…On Tue, May 21, 2019 at 3:29 AM Shiyang Wang ***@***.***> wrote:
so currently we have ocp build job to build images and push to
registry.reg-aws then build-sync job to sync to quay.io, but are we gonna
deprecated registry.reg-aws for good?
@openshift/openshift-team-automated-release
<https://github.com/orgs/openshift/teams/openshift-team-automated-release>
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#125>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHJV2QACA4B7FMZWNCBQ4DPWOQDVANCNFSM4HM3BU7A>
.
|
|
Thanks Adam for the clarification. It sounds like we will still sync images to I've heard that when Brew/OSBS pushes to quay.io, it will do that using a registry proxy application, and this application will be the only app that has permission to that namespace under quay.io. In other words, the Brew -> quay.io piece will be more-or-less invisible to everyone. How will that affect this work? |
|
I couldn't say as I had not heard that before. We're honestly still
figuring it out.
…On Thu, May 23, 2019 at 8:49 AM Ken Dreyer ***@***.***> wrote:
Thanks Adam for the clarification. It sounds like we will still sync
images to registry.reg-aws.
I've heard that when Brew/OSBS pushes to quay.io, it will do that using a
registry proxy application, and this application will be the only app that
has permission to that namespace under quay.io. In other words, the Brew
-> quay.io piece will be more-or-less invisible to everyone.
How will that affect this work?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#125>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHJV2SLYDGX75LJZOATC7TPW2HDPANCNFSM4HM3BU7A>
.
|
|
I am familiar with the quay proxy. A namespace on quay.io is replacing all of brew-pulp. As such only OSBS will be able to push to it, and it will not be publicly available. We will not access it directly; instead there will be a registry proxy that can be used for pull access inside the firewall. Having it on quay.io will not be appreciably different from a functional/access standpoint, except that we will access a different URL and should be a heck of a lot faster. |
|
@sosiouxme , with that information, do you expect ART to deprecate |
|
@ktdreyer I think OCP will continue to sync at least 3.11 images to However an organization with private repos on quay.io would likely be a better long-term solution (as reg-aws wanes in usage with 4.x not using it). Unfortunately you can't just use the images where OSBS will be pushing them on quay.io; they'll have to be synced somewhere else. |
|
@ktdreyer I doubt reg-aws will outlive 3.11. The same team that runs reg-aws will be running quay.io at that point and reg-aws' value will be vanishingly small. Perhaps you could establish a private repo on quay for OCS image testing? |
|
Thanks, we have https://quay.io/repository/rhceph-dev , and I was curious if there is any way to share infrastructure further with you so that we do not have this duplication. Maybe we can discuss this some other time. |
|
Hi @ktdreyer , is this issue still relevant? (i'm asking because it is quite old and I have no idea about reg-aws migration). |
|
we're actually still pushing things to reg-aws even for 4.y, mostly due to momentum. but i doubt we want to add anything more. |
We added the following sentence to the readme recently:
I heard a rumor that we're migrating away from
registry.reg-awsand hosting prerelease images on quay.io instead.How should the README text change here?
The text was updated successfully, but these errors were encountered: