Parent folderOpen Confluence

RWS Architecture article

Red Hat Quay 3.17 Management (Summary)

Red Hat management documentation covers Quay configuration, TLS, action logs, Clair, mirroring workers, OIDC, keyless robot-account authentication, metrics, health checks, backup,

  1. Typesource
  2. Statusactive
  3. Domainplatform
On this page
  1. Source - Red Hat Quay 3.17 Management
  2. Overview
  3. Context
  4. Decisions
  5. Current State
  6. References
  7. Future Work
  8. Related

Source - Red Hat Quay 3.17 Management

Overview

Red Hat management documentation covers Quay configuration, TLS, action logs, Clair, mirroring workers, OIDC, keyless robot-account authentication, metrics, health checks, backup, restore, migration, and lifecycle operations.

Context

This source is used for the operational architecture of the DC 3.0 registry service. It informs monitoring, identity integration, backup evidence, mirroring runbooks, and day-2 readiness for Red Hat Quay.

Decisions

RWS architecture implications derived from this source:

  • Expose and scrape the Operator-managed quay-metrics endpoint and include registry usage, push/pull, authentication, mirroring, and garbage-collection signals in platform observability.
  • Use OIDC integration with the target IAM service, mapped locally to Keycloak, instead of local accounts for human access.
  • Treat backup scope as the Quay configuration bundle, PostgreSQL database, and object-storage blobs; Kubernetes manifests alone are not a recoverable service backup.
  • Configure TLS for registry endpoints and backend dependencies, with certificate ownership aligned to public-key-infrastructure and cert-manager.
  • Operate mirror workers and robot-account credentials as part of day-2 service management for upstream-to-main, main-to-DCS, and tenant-facing cross-datacenter synchronization.

Current State

The source fills operational gaps in the earlier SBB stub. It still leaves RWS-specific ownership, runbook repository, and recovery-time objectives to be confirmed by the service owner.

References

  • Manage Red Hat Quay, version 3.17: Red Hat documentation
  • Relevant sections: SSL/TLS, OIDC, keyless robot accounts, metrics, health checks, mirroring, backup and restore, and migration to OpenShift.

Future Work

  • Add runbook links after the Quay service is onboarded into the platform operations catalog.
  • Confirm the alert names and dashboard ownership when monitoring is implemented.

Related