Epic Goal

• Fully automate the transition of a running Quay deployment into read-only mode declaratively via the Quay operator

Why is this important?

• The process of enabling Quay's read-only mode consists of a lot of manual steps that require access to the database and serialized orchestration
• read-only is important in order to get Quay instance into a state where they can be consistently backed up (database and object storage are in sync)
• the lack of a simple to achieve read-only mode has customers forced to a lower quality backup (crash consistent, not app consistent) by just backing up Quay's databases while its running

Scenarios

1. A Quay admin can solely rely on a toggle called spec.readOnly on the QuayRegistry object in order to control the read-only state of the registry
2. A Quay admin can rely on the status block of a QuayRegistry object to determine the progress of transitioning to read-only mode

Acceptance Criteria

• The internal implementation of the read-only is free to change, if we need to get rid of service keys, this is not a blocker

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>