Chapter 4. Deploying Red Hat Quay on premise

Example Red Hat Quay deployments include proof of concept on a single node, highly available in a single data center, and highly available across multiple data centers. You can reference these examples when planning your deployment.

The following image shows three possible deployments for Red Hat Quay:

Red Hat Quay deployment topology sends pushes, UI, and API traffic to public endpoints and serves pulls from object storage. You can use this overview to understand traffic flow in your deployment.

The following image provides a high level overview of a Red Hat Quay deployment topology:

In this deployment, all pushes, user interface, and API requests are received by public Red Hat Quay endpoints. Pulls are served directly from object storage.

Red Hat Quay deployment topology with storage proxy routes all traffic, including pulls, through the public endpoint. You can use this topology when clients cannot access object storage directly or when you need a single entry point.

The following image provides a high level overview of a Red Hat Quay deployment topology with storage proxy configured:

With storage proxy configured, all traffic passes through the public Red Hat Quay endpoint.