Skip to content

Latest commit

 

History

History
89 lines (63 loc) · 3.7 KB

README.adoc

File metadata and controls

89 lines (63 loc) · 3.7 KB
Raw

01 Quay Installation

Installing the Quay Operator

Installing the Quay Operator from the OpenShift console

  1. Using the OpenShift console, Select Operators → OperatorHub, then select the Red Hat Quay Operator. If there is more than one, be sure to use the Red Hat certified Operator and not the community version.

    operatorhub quay

  2. The Installation page outlines the features and prerequisites:

    operator install page

  3. Select Install. The Operator Installation page appears.

    operator subscription

  4. The following choices are available for customizing the installation:

    • Update Channel: Choose the update channel, for example, stable-3.6 for the latest release.

    • Installation Mode: Choose All namespaces on the cluster if you want the Operator to be available cluster-wide. Choose A specific namespace on the cluster if you want it deployed only within a single namespace. It is recommended that you install the Operator cluster-wide. If you choose a single namespace, the monitoring component will not be available by default.

    • Approval Strategy: Choose to approve either automatic or manual updates. Automatic update strategy is recommended.

  5. Select Install.

  6. After a short time, you will see the Operator installed successfully in the Installed Operators page.

Installing the Quay Operator from the CLI

$ oc apply --kustomize kustomize/quay-operator/base

Installing Quay prerequisites (out of the scope of the workshop)

OpenShift Data Foundation

  • Worker nodes must be labeled with a label cluster.ocs.openshift.io/openshift-storage=

  • The default storage class is set to gp2 (AWS)

$ oc apply --kustomize kustomize/odf-operator/base

# Wait until the odf-operator csvs are fully deployed (All csvs must reach the phase Succeeded)
$ oc get csv --namespace openshift-storage

# Deploy an ODF instance on AWS
$ oc apply --kustomize kustomize/odf-instance/overlays/aws

# Watch for the status of the Available condition to change to True
$ oc get storagecluster \
  --namespace openshift-storage \
  --output jsonpath='{.items[0].status.conditions[?(@.type=="Available")].status}'

Multi-Cloud Object Gateway

# install nooba (optional as it should have been setup already by odf)
$ oc apply --kustomize kustomize/noobaa-gateway/base
..
$ oc get -n openshift-storage noobaas noobaa -w
..
#  make the PersistentVolume backing store the default
$ oc patch bucketclass noobaa-default-bucket-class --patch '{"spec":{"placementPolicy":{"tiers":[{"backingStores":["noobaa-pv-backing-store"]}]}}}' --type merge -n openshift-storage

Deploying the Quay instance

Deploying the Quay instance from the OpenShift console

  1. Create a namespace, for example, quay-enterprise.

  2. Select Operators → Installed Operators, then select the Quay Operator to navigate to the Operator detail view.

  3. Click 'Create Instance' on the 'Quay Registry' tile under 'Provided APIs'.

  4. Optionally change the 'Name' of the QuayRegistry. This will affect the hostname of the registry. All other fields have been populated with defaults.

  5. Click 'Create' to submit the QuayRegistry to be deployed by the Quay Operator.

  6. You should be redirected to the QuayRegistry list view. Click on the QuayRegistry you just created to see the details view.

  7. Once the 'Registry Endpoint' has a value, click it to access your new Quay registry via the UI. You can now select 'Create Account' to create a user and sign in.

Deploying the Quay instance from the CLI

Use some time to familiarize with the kustomize configuration.

$ oc apply --kustomize kustomize/quay-instance/base

Navigation