Chapter 2. Red Hat Quay support
Red Hat Quay provides support for the following:
- Multiple authentication and access methods
- Multiple storage backends
-
Custom certificates for
Quay,Clair, and storage backend containers - Application registries
- Different container image types
2.1. Architecture
Red Hat Quay includes several core components, both internal and external.
For a fuller architectural breakdown, see the Red Hat Quay architecture guide.
2.1.1. Internal components
Red Hat Quay includes the following internal components:
-
Quay (container registry). Runs the
Quaycontainer as a service, consisting of several components in the pod. - Clair. Scans container images for vulnerabilities and suggests fixes.
2.1.2. External components
Red Hat Quay includes the following external components:
- Database. Used by Red Hat Quay as its primary metadata storage. Note that this is not for image storage.
- Redis (key-value store). Stores live builder logs and the Red Hat Quay tutorial. Also includes the locking mechanism that is required for garbage collection.
Cloud storage. For supported deployments, one of the following storage types must be used:
- Public cloud storage. In public cloud environments, you should use the cloud provider’s object storage, such as Amazon Web Services’s Amazon S3 or Google Cloud’s Google Cloud Storage.
- Private cloud storage. In private clouds, an S3 or Swift compliant Object Store is needed, such as Ceph RADOS, or OpenStack Swift.
Warning
Do not use "Locally mounted directory" Storage Engine for any production configurations. Mounted NFS volumes are not supported. Local storage is meant for Red Hat Quay test-only installations.
