A registry is an important part of deploying applications to OpenShift, or any Kubernetes, clusters. The registry is responsible for storing the container images created and used by applications. OpenShift has a default, built-in registry which is deployed automatically with full-stack automation deployments, a.k.a. installer provisioned infrastructure or IPI, but often requires some day 2 configuration with pre-existing infrastructure, a.k.a. user provisioned infrastructure or UPI. However, that’s not the only registry option! Red Hat Quay, Quay.io, and many other third party and partner options are available for storing your container images.
This week we invited Andrew Block, Distinguished Architect with Red Hat Consulting, to the stream to discuss the registry, different options available, the pros/cons of each, and he provided some overall advice and guidance for administering a registry.
As always, please see the list below for additional links to specific topics, questions, and supporting materials for the episode!
If you’re interested in more streaming content, please subscribe to the OpenShift.tvstreaming calendar to see the upcoming episode topics and to receive any schedule changes. If you have questions or topic suggestions for the OpenShift Administrator’s Office Hour, please contact us via Discord, Twitter, or come join us live, Wednesdays at 11am EST / 1600 UTC, on YouTube and Twitch.
Red Hat Quay - Red Hat’s standalone registry product, which can be deployed to OpenShift or separately, provides a number of benefits above and beyond the default OpenShift registry. Hear our discussion about Quay on-prem vs the OpenShift registry here in the stream.
Introduction By default, the OpenShift Container Platform registry is not exposed outside of the cluster at the time of installation. Red Hat Advanced Cluster Security can be used to scan images held ...
In part 2 of this three-part blog series, I covered a practical implementation of OpenShift Platform Plus tools and policies that help with achieving compliance with certain NIST SP 800-53 security ...