-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
quay-v3.4.0
-
False
-
False
-
Undefined
-
-
0
Description:
This is a document issue found when reviewing Quay V3.4 Operator docs. Now in Quay V3.4 the CR name is changed from QuayEcosystem to QuayRegistry, this need to be updated in whole docs, give examples below.
Issue #1:
In "Chapter 5. Customizing your Red Hat Quay cluster", need update QuayEcosystem to QuayRegistry
Although you can run a default Red Hat Quay setup by simply creating a secret and the QuayEcosystem custom resource, the following sections describe how you can modify the default setup.
Issue #2:
In "Chapter 5. Customizing your Red Hat Quay cluster", need update QuayEcosystem to QuayRegistry
NOTEIt is recommended that you also set the superusers field of the quay property in the QuayEcosystem object so as to ensure consistency between the the various properties. See the Superusers section below.
Issue #3
In "5.2. Providing persistent storage using PostgreSQL database", need update QuayEcosystem to QuayRegistry
The PostgreSQL relational database is used by default as the persistent store for Red Hat Quay. PostgreSQL can either be deployed by the Operator within the namespace or leverage an existing instance. The determination of whether to provision an instance or not within the current namespace depends on whether the server property within the QuayEcosystem is defined.
Issue #4
In "5.4.1. Overview of storage backends", need update QuayEcosystem to QuayRegistry
Storage for Red Hat Quay can be configured using the registryBackend field within the quay property in the QuayEcosystem resource which contain an array of backends. The ability to define multiple backends enables replication and high availability of images.
