Jump To Close Expand all Collapse all Table of contents Configure Red Hat Quay 1. Getting started with configuration Expand section "1. Getting started with configuration" Collapse section "1. Getting started with configuration" 1.1. Configuration updates for Quay 3.6 Expand section "1.1. Configuration updates for Quay 3.6" Collapse section "1.1. Configuration updates for Quay 3.6" 1.1.1. New configuration fields 1.1.2. Deprecated configuration fields 1.2. Editing the configuration file 1.3. Location of configuration file in a standalone deployment 1.4. Configuring Quay on OpenShift using the command line and API Expand section "1.4. Configuring Quay on OpenShift using the command line and API" Collapse section "1.4. Configuring Quay on OpenShift using the command line and API" 1.4.1. Determining QuayRegistry endpoints and secrets 1.4.2. Downloading the existing configuration 1.4.3. Using the config bundle to configure custom SSL certs 1.5. Minimal configuration Expand section "1.5. Minimal configuration" Collapse section "1.5. Minimal configuration" 1.5.1. Sample minimal configuration file 1.5.2. Local storage 1.5.3. Cloud storage 2. Configuration fields Expand section "2. Configuration fields" Collapse section "2. Configuration fields" 2.1. Required configuration fields 2.2. Automation options 2.3. Optional configuration fields 2.4. General required fields 2.5. Database configuration Expand section "2.5. Database configuration" Collapse section "2.5. Database configuration" 2.5.1. Database URI 2.5.2. Database connection arguments Expand section "2.5.2. Database connection arguments" Collapse section "2.5.2. Database connection arguments" 2.5.2.1. PostgreSQL SSL connection arguments 2.5.2.2. MySQL SSL connection arguments 2.6. Image storage Expand section "2.6. Image storage" Collapse section "2.6. Image storage" 2.6.1. Image storage features 2.6.2. Image storage configuration fields 2.6.3. Local storage 2.6.4. OCS/NooBaa 2.6.5. Ceph / RadosGW Storage / Hitachi HCP 2.6.6. AWS S3 storage 2.6.7. Google cloud storage 2.6.8. Azure storage 2.6.9. Swift storage 2.7. Redis configuration fields Expand section "2.7. Redis configuration fields" Collapse section "2.7. Redis configuration fields" 2.7.1. Build logs 2.7.2. User events 2.7.3. Example redis configuration 2.8. Tag expiration options 2.9. Pre-configuring Quay for automation Expand section "2.9. Pre-configuring Quay for automation" Collapse section "2.9. Pre-configuring Quay for automation" 2.9.1. Allowing the API to create the first user 2.9.2. Enabling general API access 2.9.3. Adding a super user 2.9.4. Restricting user creation 2.9.5. Suggested configuration for automation 2.9.6. Deploying the Operator using the initial configuration 2.9.7. Using the API to create the first user Expand section "2.9.7. Using the API to create the first user" Collapse section "2.9.7. Using the API to create the first user" 2.9.7.1. Invoking the API 2.9.7.2. Using the OAuth token Expand section "2.9.7.2. Using the OAuth token" Collapse section "2.9.7.2. Using the OAuth token" 2.9.7.2.1. Create organization 2.9.7.2.2. Get organization details 2.10. Basic configuration 2.11. SSL configuration fields Expand section "2.11. SSL configuration fields" Collapse section "2.11. SSL configuration fields" 2.11.1. Configuring SSL 2.12. Adding TLS Certificates to the Red Hat Quay Container Expand section "2.12. Adding TLS Certificates to the Red Hat Quay Container" Collapse section "2.12. Adding TLS Certificates to the Red Hat Quay Container" 2.12.1. Add TLS certificates to Red Hat Quay 2.13. LDAP configuration fields Expand section "2.13. LDAP configuration fields" Collapse section "2.13. LDAP configuration fields" 2.13.1. LDAP configuration example 2.14. Mirroring configuration fields 2.15. Security scanner configuration fields 2.16. OCI and Helm configuration 2.17. Action log configuration fields Expand section "2.17. Action log configuration fields" Collapse section "2.17. Action log configuration fields" 2.17.1. Action log storage configuration 2.17.2. Action log rotation and archiving configuration 2.18. Build logs 2.19. Dockerfile build triggers fields Expand section "2.19. Dockerfile build triggers fields" Collapse section "2.19. Dockerfile build triggers fields" 2.19.1. GitHub build triggers 2.19.2. BitBucket build triggers 2.19.3. GitLab build triggers 2.20. OAuth configuration Expand section "2.20. OAuth configuration" Collapse section "2.20. OAuth configuration" 2.20.1. GitHub OAuth 2.20.2. Google OAuth 2.21. Configuring nested repositories 2.22. Adding other OCI media types to Quay 2.23. Mail configuration 2.24. User configuration fields 2.25. Recaptcha configuration 2.26. ACI configuration 2.27. JTW configuration 2.28. App tokens 2.29. Miscellaneous fields 2.30. Legacy configuration fields 3. Environment variables Expand section "3. Environment variables" Collapse section "3. Environment variables" 3.1. Geo-replication 3.2. Database connection pooling 3.3. HTTP connection counts 3.4. Worker count variables 4. Using the config tool to reconfigure Quay on OpenShift Expand section "4. Using the config tool to reconfigure Quay on OpenShift" Collapse section "4. Using the config tool to reconfigure Quay on OpenShift" 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 in to the config editor 4.1.3. Changing configuration 4.2. Monitoring reconfiguration in the UI Expand section "4.2. Monitoring reconfiguration in the UI" Collapse section "4.2. Monitoring reconfiguration in the UI" 4.2.1. QuayRegistry resource 4.2.2. Events 4.3. Accessing updated information after reconfiguration Expand section "4.3. Accessing updated information after reconfiguration" Collapse section "4.3. Accessing updated information after reconfiguration" 4.3.1. Accessing the updated config tool credentials in the UI 4.3.2. Accessing the updated config.yaml in the UI 5. Quay Operator components Expand section "5. Quay Operator components" Collapse section "5. Quay Operator components" 5.1. Using managed components 5.2. Using unmanaged components for dependencies Expand section "5.2. Using unmanaged components for dependencies" Collapse section "5.2. Using unmanaged components for dependencies" 5.2.1. Using an existing Postgres database 5.2.2. NooBaa unmanaged storage 5.2.3. Disabling the Horizontal Pod Autoscaler 5.3. Add certs when deployed on Kubernetes 5.4. Configuring OCI and Helm with the Operator 5.5. Volume size overrides 6. Using the configuration API Expand section "6. Using the configuration API" Collapse section "6. Using the configuration API" 6.1. Retrieving the default configuration 6.2. Retrieving the current configuration 6.3. Validating configuration using the API 6.4. Determining the required fields 7. Using the configuration tool Expand section "7. Using the configuration tool" Collapse section "7. Using the configuration tool" 7.1. Custom SSL certificates UI 7.2. Basic configuration Expand section "7.2. Basic configuration" Collapse section "7.2. Basic configuration" 7.2.1. Contact information 7.3. Server configuration Expand section "7.3. Server configuration" Collapse section "7.3. Server configuration" 7.3.1. Server configuration choice 7.3.2. TLS configuration 7.4. Database configuration Expand section "7.4. Database configuration" Collapse section "7.4. Database configuration" 7.4.1. PostgreSQL configuration 7.5. Data consistency 7.6. Time machine configuration 7.7. Redis configuration 7.8. Repository mirroring configuration 7.9. Registry storage configuration Expand section "7.9. Registry storage configuration" Collapse section "7.9. Registry storage configuration" 7.9.1. Enable storage replication 7.9.2. Storage engines Expand section "7.9.2. Storage engines" Collapse section "7.9.2. Storage engines" 7.9.2.1. Local storage 7.9.2.2. Amazon S3 storage 7.9.2.3. Azure blob storage 7.9.2.4. Google cloud storage 7.9.2.5. Ceph object gateway (RADOS) storage 7.9.2.6. OpenStack (Swift) storage configuration 7.9.2.7. Cloudfront + Amazon S3 storage configuration 7.10. Action log configuration Expand section "7.10. Action log configuration" Collapse section "7.10. Action log configuration" 7.10.1. Action log storage configuration Expand section "7.10.1. Action log storage configuration" Collapse section "7.10.1. Action log storage configuration" 7.10.1.1. Database action log storage 7.10.1.2. Elasticsearch action log storage 7.10.2. Action log rotation and archiving 7.11. Security scanner configuration 7.12. Application registry configuration 7.13. Email configuration 7.14. Internal authentication configuration Expand section "7.14. Internal authentication configuration" Collapse section "7.14. Internal authentication configuration" 7.14.1. LDAP 7.14.2. Keystone (OpenStack identity) 7.14.3. JWT custom authentication 7.14.4. External application token 7.15. External authentication (OAUTH) configuration Expand section "7.15. External authentication (OAUTH) configuration" Collapse section "7.15. External authentication (OAUTH) configuration" 7.15.1. GitHub (Enterprise) authentication 7.15.2. Google authentication 7.16. Access settings configuration 7.17. Dockerfile build support Expand section "7.17. Dockerfile build support" Collapse section "7.17. Dockerfile build support" 7.17.1. GitHub (Enterprise) Build Triggers 7.17.2. BitBucket Build Triggers 7.17.3. GitLab Build Triggers 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 Configure Red Hat Quay Red Hat Quay 3.6Customizing Red Hat Quay using configuration optionsRed Hat OpenShift Documentation TeamLegal NoticeAbstract Configure Red Hat Quay Next