Project Quay is a security-focused, scalable private registry for managing container images and OCI artifacts across distributed environments. You can use it with OpenShift Container Platform and Kubernetes to store, build, distribute, and scan images for vulnerabilities.
About Project Quay
Project Quay is a security-focused container registry platform for storing, distributing, and governing container images and other OCI artifacts. You can deploy it as a standalone component or as an Operator on OpenShift Container Platform, and use it to deliver containerized software across OpenShift Container Platform and Kubernetes clusters in development and production.
Project Quay provides a single, resilient content repository with a web interface, access controls, and Continuous Integration/Continuous Deployment (CI/CD) integrations. Teams can upload and manage images in private repositories. Administrators can control who can view or change content and share images with designated teams.
Project Quay addresses container security through Clair, which scans images for known vulnerabilities and suggests remediation. The platform also integrates with CI/CD tools so that you can automate build and deployment workflows.
Project Quay supports multiple authentication and access methods, storage backends, and container image types, including custom certificates for Quay, Clair, and storage backends. It also supports small-scale and enterprise deployments. High availability configurations help organizations rely on the registry for mission-critical applications, and replication and distribution mechanisms deliver images across geographical locations.
Project Quay is regularly released with new features, bug fixes, and software updates.
Project Quay features
Project Quay provides enterprise registry capabilities for storing, distributing, securing, and automating container images and OCI artifacts. The following features highlight common capabilities for current releases. The list is not exhaustive; see the Project Quay release notes for the latest information.
Scalability and high availability
Project Quay can run as a highly available registry on premise or in the cloud. You can scale deployments to handle significant image traffic while keeping the registry available for development and production workloads.
Content distribution
Project Quay helps you deliver images in multiple ways:
-
Repository mirroring. Synchronize images from Project Quay or other registries into your Project Quay deployment based on repository names and tags.
-
Geo-replication. Present multiple geographically distributed Project Quay deployments as a single registry, with asynchronous replication and transparent client failover.
-
Disconnected environments. Deploy Project Quay in air-gapped or partially connected environments when you need registry access without full internet connectivity.
Security and access control
Project Quay includes Clair for vulnerability scanning of container images, with insights into known issues and suggested remediation. You can also configure TLS, isolate build workloads, and use organization and team role-based access controls to manage who can view or change registry content.
Build and CI/CD automation
Project Quay integrates with Continuous Integration/Continuous Deployment (CI/CD) tools and Git-compatible systems. You can automate image builds and deployments, including build triggers such as GitHub webhooks when code is committed.
Image and artifact support
Project Quay stores and distributes container images and other OCI artifacts. It supports Docker v2, schema 2, including multi-architecture images, so teams can manage diverse workloads in one registry.
Day-2 operations
Project Quay includes operational capabilities such as custom log rotation and zero-downtime garbage collection. Red Hat provides 24/7 support for Project Quay.