Leverage registry.redhat.io for product builds
See original GitHub issueWe need to move from registry.access.redhat.com
to registry.redhat.io
in all cases where the product registry is referenced. I think this is first and foremost an issues for the scripts in https://github.com/syndesisio/fuse-online-install, but may also impact other places (i.e. syndesis).
The new registry requires authentication.
Issue Analytics
- State:
- Created 5 years ago
- Comments:47 (16 by maintainers)
Top Results From Across the Web
Transitioning the Red Hat container registry
To support our existing users and users to come, we will be transitioning our product portfolio and customers to a new container registry...
Read more >Introducing Mirror Registry for Red Hat OpenShift
The mirror registry for Red Hat OpenShift is built on top of the Red ... node that leverages a local database and local...
Read more >Using Images OpenShift Container Platform 3.11
Red Hat's official container images are provided in the Red Hat Registry at registry.redhat.io. OpenShift Container Platform's supported S2I, database, ...
Read more >Use Red Hat Quay
Red Hat Quay container image registries let you store container images in a ... Hat Quay manages builds and provides the same mechanism...
Read more >How to use entitled image builds to build DriverContainers ...
We can leverage a Red Hat subscription also when building container images, which is named here during the blog as an entitled build....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rhuss I think the
fuse-online-install
install_ocp.sh
andupdate_ocp.sh
are the tho missing bits, and we(heiko+myself) are taking care of it already@heiko-braun I think this replicates the behaviour of
oc link
without--for-pull
, that is the secret is both referenced in the pull and mountable secrets.