update README for registry.reg-aws migration about ocp-build-data HOT 11 CLOSED

If your images are in dist-git, then ART has a service that can mirror your images once a day to registry.reg-aws

we have a job called build-maint to do that, but it only sync branch sync-misc not openshift-3.x or openshift-4.x, it's just a small feature not for official ocp release.

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 deprecate registry.reg-aws for good? @openshift/openshift-team-automated-release

from ocp-build-data.

from ocp-build-data.

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?

from ocp-build-data.

from ocp-build-data.

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.

from ocp-build-data.

@sosiouxme , with that information, do you expect ART to deprecate registry.reg-aws in the future? We'd very much like to have an "official" way to sync OCS internal images to a protected registry so we can test in AWS.

from ocp-build-data.

@ktdreyer I think OCP will continue to sync at least 3.11 images to registry.reg-aws until it EOLs in 2022, so that QE can test updates. @jupierce may be able to comment as to whether it can be re-used for images outside core OCP.

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.

from ocp-build-data.

@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?

from ocp-build-data.

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.

from ocp-build-data.

Hi @ktdreyer , is this issue still relevant? (i'm asking because it is quite old and I have no idea about reg-aws migration).

from ocp-build-data.

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.

from ocp-build-data.