Jump To Close Expand all Collapse all Table of contents Red Hat Quay Operator features 1. Federal Information Processing Standard (FIPS) readiness and compliance Expand section "1. Federal Information Processing Standard (FIPS) readiness and compliance" Collapse section "1. Federal Information Processing Standard (FIPS) readiness and compliance" 1.1. Enabling FIPS compliance 2. Console monitoring and alerting Expand section "2. Console monitoring and alerting" Collapse section "2. Console monitoring and alerting" 2.1. Dashboard 2.2. Metrics 2.3. Alerting 3. Configuring Red Hat Quay on OpenShift Container Platform Expand section "3. Configuring Red Hat Quay on OpenShift Container Platform" Collapse section "3. Configuring Red Hat Quay on OpenShift Container Platform" 3.1. Editing the config bundle secret in the OpenShift Container Platform console 3.2. Determining QuayRegistry endpoints and secrets Expand section "3.2. Determining QuayRegistry endpoints and secrets" Collapse section "3.2. Determining QuayRegistry endpoints and secrets" 3.2.1. Locating the username and password for the config editor tool 3.3. Downloading the existing configuration Expand section "3.3. Downloading the existing configuration" Collapse section "3.3. Downloading the existing configuration" 3.3.1. Using the config editor endpoint to download the existing configuration 3.3.2. Using the config bundle secret to download the existing configuration 3.4. Using the config bundle to configure custom SSL/TLS certs 4. Using the config tool to reconfigure Red Hat Quay on OpenShift Container Platform Expand section "4. Using the config tool to reconfigure Red Hat Quay on OpenShift Container Platform" Collapse section "4. Using the config tool to reconfigure Red Hat Quay on OpenShift Container Platform" 4.1. Accessing the config editor Expand section "4.1. Accessing the config editor" Collapse section "4.1. Accessing the config editor" 4.1.1. Retrieving the config editor credentials 4.1.2. Logging into the config editor 4.1.3. Changing configuration 4.2. Monitoring reconfiguration in the Red Hat Quay UI Expand section "4.2. Monitoring reconfiguration in the Red Hat Quay UI" Collapse section "4.2. Monitoring reconfiguration in the Red Hat Quay UI" 4.2.1. QuayRegistry resource 4.2.2. Events 4.3. Accessing updated information after reconfiguration 4.4. Custom SSL/TLS certificates UI 4.5. External Access to the Registry 4.6. QuayRegistry API 5. Clair for Red Hat Quay Expand section "5. Clair for Red Hat Quay" Collapse section "5. Clair for Red Hat Quay" 5.1. Clair vulnerability databases 5.2. Clair on OpenShift Container Platform 5.3. Testing Clair 5.4. Advanced Clair configuration Expand section "5.4. Advanced Clair configuration" Collapse section "5.4. Advanced Clair configuration" 5.4.1. Unmanaged Clair configuration Expand section "5.4.1. Unmanaged Clair configuration" Collapse section "5.4.1. Unmanaged Clair configuration" 5.4.1.1. Running a custom Clair configuration with an unmanaged Clair database 5.4.1.2. Configuring a custom Clair database with an unmanaged Clair database 5.4.2. Running a custom Clair configuration with a managed Clair database Expand section "5.4.2. Running a custom Clair configuration with a managed Clair database" Collapse section "5.4.2. Running a custom Clair configuration with a managed Clair database" 5.4.2.1. Setting a Clair database to managed 5.4.2.2. Configuring a custom Clair database with a managed Clair configuration 5.4.3. Clair in disconnected environments Expand section "5.4.3. Clair in disconnected environments" Collapse section "5.4.3. Clair in disconnected environments" 5.4.3.1. Setting up Clair in a disconnected OpenShift Container Platform cluster Expand section "5.4.3.1. Setting up Clair in a disconnected OpenShift Container Platform cluster" Collapse section "5.4.3.1. Setting up Clair in a disconnected OpenShift Container Platform cluster" 5.4.3.1.1. Installing the clairctl command line utility tool for OpenShift Container Platform deployments 5.4.3.1.2. Retrieving and decoding the Clair configuration secret for Clair deployments on OpenShift Container Platform 5.4.3.1.3. Exporting the updaters bundle from a connected Clair instance 5.4.3.1.4. Configuring access to the Clair database in the disconnected OpenShift Container Platform cluster 5.4.3.1.5. Importing the updaters bundle into the disconnected OpenShift Container Platform cluster 5.4.3.2. Setting up a self-managed deployment of Clair for a disconnected OpenShift Container Platform cluster Expand section "5.4.3.2. Setting up a self-managed deployment of Clair for a disconnected OpenShift Container Platform cluster" Collapse section "5.4.3.2. Setting up a self-managed deployment of Clair for a disconnected OpenShift Container Platform cluster" 5.4.3.2.1. Installing the clairctl command line utility tool for a self-managed Clair deployment on OpenShift Container Platform 5.4.3.2.2. Deploying a self-managed Clair container for disconnected OpenShift Container Platform clusters 5.4.3.2.3. Exporting the updaters bundle from a connected Clair instance 5.4.3.2.4. Configuring access to the Clair database in the disconnected OpenShift Container Platform cluster 5.4.3.2.5. Importing the updaters bundle into the disconnected OpenShift Container Platform cluster 5.4.4. Enabling Clair CRDA 5.4.5. Mapping repositories to Common Product Enumeration information Expand section "5.4.5. Mapping repositories to Common Product Enumeration information" Collapse section "5.4.5. Mapping repositories to Common Product Enumeration information" 5.4.5.1. Mapping repositories to Common Product Enumeration example configuration 5.5. Deploying Red Hat Quay on infrastructure nodes Expand section "5.5. Deploying Red Hat Quay on infrastructure nodes" Collapse section "5.5. Deploying Red Hat Quay on infrastructure nodes" 5.5.1. Labeling and tainting nodes for infrastructure use 5.5.2. Creating a project with node selector and tolerations 5.5.3. Installing the Red Hat Quay Operator in the namespace 5.5.4. Creating the Red Hat Quay registry 5.6. Enabling monitoring when the Red Hat Quay Operator is installed in a single namespace Expand section "5.6. Enabling monitoring when the Red Hat Quay Operator is installed in a single namespace" Collapse section "5.6. Enabling monitoring when the Red Hat Quay Operator is installed in a single namespace" 5.6.1. Creating a cluster monitoring config map 5.6.2. Creating a user-defined workload monitoring ConfigMap object 5.6.3. Enable monitoring for user-defined projects 5.6.4. Creating a Service object to expose Red Hat Quay metrics 5.6.5. Creating a ServiceMonitor object 5.6.6. Viewing metrics in OpenShift Container Platform 5.7. Resizing Managed Storage Expand section "5.7. Resizing Managed Storage" Collapse section "5.7. Resizing Managed Storage" 5.7.1. Resizing the NooBaa PVC 5.8. Customizing Default Operator Images Expand section "5.8. Customizing Default Operator Images" Collapse section "5.8. Customizing Default Operator Images" 5.8.1. Environment Variables 5.8.2. Applying overrides to a running Operator 5.9. AWS S3 CloudFront 6. Red Hat Quay build enhancements Expand section "6. Red Hat Quay build enhancements" Collapse section "6. Red Hat Quay build enhancements" 6.1. Red Hat Quay build limitations 6.2. Creating a Red Hat Quay builders environment with OpenShift Container Platform Expand section "6.2. Creating a Red Hat Quay builders environment with OpenShift Container Platform" Collapse section "6.2. Creating a Red Hat Quay builders environment with OpenShift Container Platform" 6.2.1. OpenShift Container Platform TLS component 6.2.2. Using OpenShift Container Platform for Red Hat Quay builders Expand section "6.2.2. Using OpenShift Container Platform for Red Hat Quay builders" Collapse section "6.2.2. Using OpenShift Container Platform for Red Hat Quay builders" 6.2.2.1. Preparing OpenShift Container Platform for virtual builders 6.2.2.2. Manually adding SSL/TLS certificates Expand section "6.2.2.2. Manually adding SSL/TLS certificates" Collapse section "6.2.2.2. Manually adding SSL/TLS certificates" 6.2.2.2.1. Creating and signing certificates 6.2.2.2.2. Setting TLS to unmanaged 6.2.2.2.3. Creating temporary secrets 6.2.2.2.4. Copying secret data to the configuration YAML 6.2.2.3. Using the UI to create a build trigger 6.2.2.4. Modifying your AWS S3 storage bucket 6.2.2.5. Modifying your Google Cloud Platform object bucket 7. Geo-replication Expand section "7. Geo-replication" Collapse section "7. Geo-replication" 7.1. Geo-replication features 7.2. Geo-replication requirements and constraints Expand section "7.2. Geo-replication requirements and constraints" Collapse section "7.2. Geo-replication requirements and constraints" 7.2.1. Setting up geo-replication on OpenShift Container Platform Expand section "7.2.1. Setting up geo-replication on OpenShift Container Platform" Collapse section "7.2.1. Setting up geo-replication on OpenShift Container Platform" 7.2.1.1. Configuring geo-replication for the Red Hat Quay Operator on OpenShift Container Platform 7.2.2. Mixed storage for geo-replication 7.3. Upgrading a geo-replication deployment of the Red Hat Quay Operator Expand section "7.3. Upgrading a geo-replication deployment of the Red Hat Quay Operator" Collapse section "7.3. Upgrading a geo-replication deployment of the Red Hat Quay Operator" 7.3.1. Removing a geo-replicated site from your Red Hat Quay Operator deployment 8. Backing up and restoring Red Hat Quay managed by the Red Hat Quay Operator Expand section "8. Backing up and restoring Red Hat Quay managed by the Red Hat Quay Operator" Collapse section "8. Backing up and restoring Red Hat Quay managed by the Red Hat Quay Operator" 8.1. Backing up Red Hat Quay Expand section "8.1. Backing up Red Hat Quay" Collapse section "8.1. Backing up Red Hat Quay" 8.1.1. Red Hat Quay configuration backup 8.1.2. Scaling down your Red Hat Quay deployment 8.1.3. Backing up the Red Hat Quay managed database Expand section "8.1.3. Backing up the Red Hat Quay managed database" Collapse section "8.1.3. Backing up the Red Hat Quay managed database" 8.1.3.1. Backing up the Red Hat Quay managed object storage 8.1.4. Scale the Red Hat Quay deployment back up 8.2. Restoring Red Hat Quay Expand section "8.2. Restoring Red Hat Quay" Collapse section "8.2. Restoring Red Hat Quay" 8.2.1. Restoring Red Hat Quay and its configuration from a backup 8.2.2. Scaling down your Red Hat Quay deployment 8.2.3. Restoring your Red Hat Quay database 8.2.4. Restore your Red Hat Quay object storage data 8.2.5. Scaling up your Red Hat Quay deployment 9. Enabling OCI support with the Red Hat Quay Operator 10. Volume size overrides 11. Scanning pod images with the Container Security Operator Expand section "11. Scanning pod images with the Container Security Operator" Collapse section "11. Scanning pod images with the Container Security Operator" 11.1. Downloading and running the Container Security Operator in OpenShift Container Platform 11.2. Query image vulnerabilities from the CLI 12. Deploying IPv6 on the Red Hat Quay Operator Expand section "12. Deploying IPv6 on the Red Hat Quay Operator" Collapse section "12. Deploying IPv6 on the Red Hat Quay Operator" 12.1. Enabling the IPv6 protocol family 12.2. IPv6 limitations 13. Adding custom SSL/TLS certificates when Red Hat Quay is deployed on Kubernetes 14. Upgrading the Red Hat Quay Operator Overview Expand section "14. Upgrading the Red Hat Quay Operator Overview" Collapse section "14. Upgrading the Red Hat Quay Operator Overview" 14.1. Operator Lifecycle Manager 14.2. Upgrading the Quay Operator Expand section "14.2. Upgrading the Quay Operator" Collapse section "14.2. Upgrading the Quay Operator" 14.2.1. Upgrading Quay 14.2.2. Updating Red Hat Quay from 3.8 → 3.9 14.2.3. Upgrading directly from 3.3.z or 3.4.z to 3.6 Expand section "14.2.3. Upgrading directly from 3.3.z or 3.4.z to 3.6" Collapse section "14.2.3. Upgrading directly from 3.3.z or 3.4.z to 3.6" 14.2.3.1. Upgrading with edge routing enabled 14.2.3.2. Upgrading with custom SSL/TLS certificate/key pairs without Subject Alternative Names 14.2.3.3. Configuring Clair v4 when upgrading from 3.3.z or 3.4.z to 3.6 using the Red Hat Quay Operator 14.2.4. Swift configuration when upgrading from 3.3.z to 3.6 14.2.5. Changing the update channel for the Red Hat Quay Operator 14.2.6. Manually approving a pending Operator upgrade 14.3. Upgrading a QuayRegistry 14.4. Upgrading a QuayEcosystem Expand section "14.4. Upgrading a QuayEcosystem" Collapse section "14.4. Upgrading a QuayEcosystem" 14.4.1. Reverting QuayEcosystem Upgrade 14.4.2. Supported QuayEcosystem Configurations for Upgrades Legal Notice Settings Close Language: 日本語 简体中文 English Language: 日本語 简体中文 English Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Language and Page Formatting Options Language: 日本語 简体中文 English Language: 日本語 简体中文 English Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Red Hat Quay Operator features Red Hat Quay 3.9Advanced Red Hat Quay Operator featuresRed Hat OpenShift Documentation TeamLegal NoticeAbstract Advanced Red Hat Quay Operator features Next