Chapter 1. Overview
Features of Red Hat Quay include:
- High availability
- Repository mirroring
- Docker v2, schema 2 (multiarch) support
- Continuous integration
- Security scanning with Clair
- Custom log rotation
- Zero downtime garbage collection
- 24/7 support
Red Hat Quay provides support for:
- Multiple authentication and access methods
- Multiple storage backends
- Custom certificates for Quay, Clair, and storage backends
- Application registries
- Different container image types
Red Hat Quay consists of a number of core components, both internal and external.
1.1.1. 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.
1.1.2. 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.
Cloud storage:For supported deployments, you need to use one of the following types of storage:
- 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.
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.