Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions deploy_quay_on_openshift_op/master.adoc
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
include::modules/attributes.adoc[]

[id='deploy-quay-on-openshift']
= Deploy {productname} on OpenShift with Quay Setup Operator
= Deploy {productname} on OpenShift with Quay Operator

{productname} is an enterprise-quality container registry. Use {productname} to build and
store container images, then make them available to deploy across your enterprise.

Red Hat currently supports two approaches to deploying {productname} on OpenShift:

* **Deploy {productname} with the {productname} Setup Operator**:
The {productname} Setup Operator provides a simple method to deploy and
* **Deploy {productname} on OpenShift with Quay Operator**:
The Quay Operator provides a simple method to deploy and
manage a {productname} cluster.
This is the now preferred procedure for deploying {productname} on OpenShift
and is covered in this guide.
Expand All @@ -18,6 +18,11 @@ and is covered in this guide.
provides a set of yaml files that you deploy individually to set up your {productname} cluster.
This procedure is expected to eventually be deprecated.

As of {productname} v3.3, this operator changed from the "Quay Setup Operator" to simply
the "Quay Operator." That is because the operator can now be used for more that just
initially deploying {productname}, but can also be used for on-going configuration
and maintenance of a {productname} cluster.

include::modules/con_quay_intro.adoc[leveloffset=+1]

include::modules/con_quay_openshift_prereq.adoc[leveloffset=+1]
Expand Down
2 changes: 1 addition & 1 deletion modules/con_deploy_quay_start_using.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2,5 +2,5 @@
With {productname} now running, you can:

* Select Tutorial from the Quay home page to try the 15-minute tutorial. In the tutorial, you learn to log into Quay, start a container, create images, push repositories, view repositories, and change repository permissions with Quay.
* Refer to the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/use_red_hat_quay/[Use {productname}] for information on working
* Refer to the link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/use_red_hat_quay/[Use {productname}] for information on working
with {productname} repositories.
5 changes: 4 additions & 1 deletion modules/con_quay_intro.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Features of {productname} include:

* High availability
* Geo-replication
* Repository mirroring (link:https://access.redhat.com/support/offerings/techpreview[Technology Preview] in {productname} v3.1, supported in v3.2)
* Repository mirroring
* Docker v2, schema 2 (multiarch) support
* Continuous integration
* Security scanning with Clair
Expand Down Expand Up @@ -35,4 +35,7 @@ For supported deployments, you need to use one of the following types of storage

* **Private cloud storage**: In private clouds, an S3 or Swift compliant Object Store is needed, such as Ceph RADOS, or OpenStack Swift.

[WARNING]
====
Do not use "Locally mounted directory" Storage Engine for any production configurations. Mounted NFS volumes are not supported. Local storage is meant for {productname} test-only installations.
====
10 changes: 6 additions & 4 deletions modules/con_quay_openshift_prereq.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,13 @@
Here are a few things you need to know before you begin
the {productname} on OpenShift deployment:

* *OpenShift cluster*: You need a privileged account to an OpenShift 3.x or 4.x cluster on which to deploy
* *OpenShift cluster*: You need a privileged account to an OpenShift 4.2 or later
cluster on which to deploy
the {productname}. That account must have the ability to create namespaces at the cluster scope.
To use {productname} builders, OpenShift 3 is required.

* *Storage*: AWS cloud storage is used as an example in the following procedure.
As an alternative, you can create Ceph cloud storage using steps
from the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/deploy_red_hat_quay_-_high_availability/#set_up_ceph[Set up Ceph] section of the high availability {productname} deployment guide.
from the link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/deploy_red_hat_quay_-_high_availability/#set_up_ceph[Set up Ceph] section of the high availability {productname} deployment guide.
The following is a list of other supported cloud storage:

** Amazon S3 (see link:https://access.redhat.com/solutions/3680151[S3 IAM Bucket Policy] for details on configuring an S3 bucket policy for {productname})
Expand All @@ -20,7 +20,7 @@ The following is a list of other supported cloud storage:
** Ceph Object Gateway (RADOS)
** OpenStack Swift
** CloudFront + S3
** NooBaa S3 Storage (See link:https://access.redhat.com/articles/4356091[Configuring Red Hat OpenShift Container Storage for Red Hat Quay], currently link:https://access.redhat.com/support/offerings/techpreview[Technology Preview])
** OpenShift Container Storage (NooBaa S3 Storage). (See link:https://access.redhat.com/articles/4356091[Configuring Red Hat OpenShift Container Storage for Red Hat Quay])

* *Services*: The OpenShift cluster must have enough capacity to run
the following containerized services:
Expand All @@ -43,3 +43,5 @@ for details on support for third-party databases and other components.
tutorial content to your {productname} configuration.

** *{productname}*: The quay container provides the features to manage the {productname} registry.

** *Clair*: The clair-jwt container provides Clair scanning services for the registry.
Loading