Red Hat OpenShift Quay | OpenShift, 4 Feb 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Unmanaged Components with Red Hat Quay on OpenShift

Description

The new Quay Operator shipping with Red Hat Quay 3.4 handles all of the work to install and deploy a fully functional Quay installation on Red Hat OpenShift in minutes.

It does this by completely managing each of the components needed to run Quay. But sometimes you want to install Quay without a managed component, or even have it use an existing component such as your own database instead. This demo will show how to specify unmanaged components as part of a Quay Operator installation of Red Hat Quay on Red Hat OpenShift.

Learn more at openshift.com

A

In this demo, we will showcase how to deploy quay on openshift with an externally managed database using the quay operator, make sure you've watched the video showing the batteries included quay installed before this one.

A

By default, when a cray registry is created, the quay operator assumes all components should be enabled and managed. However, there are times when you want kuey to use an existing piece of infrastructure such as an rds database. Additionally, you might want to disable container image security scanning for your registry.

A

In both cases, the solution is to mark that component. As unmanaged for this demo, we have a postgres database running on google cloud platform that we would like to use for our quay installation instead of the operator, managed database, which would be deployed on the same kubernetes clusters as quay.

A

First, we'll create a quay registry object like normal, except we want to disable clear image security scanning this time. To do this, we mark the clear component as unmanaged.

A

This tells the operator not to deploy any clear, related resources and to add or remove the necessary values to quase config.

A

We'll leave the postgres component as managed initially and then use the config editor to unmanage it once everything is deployed.

A

Let's wait until quay is fully deployed.

A

Notice there are no clear pods.

A

Created quay is up and running. Let's use the quay config editor to provide connection details to our gcp database.

A

A

The config editor is protected by password, which can be found in a secret referenced by status.config editor credentials, secret.

A

Let's find the database section of the config and fill in our details, we need to mark the database as unmanaged in order to edit the fields.

A

Now we'll have the config editor validate our.

A

Input great our input is validated now we'll submit our new config to the quay operator, which will take care of creating a new config bundle secret mounting it into the quay app pods and initiating the rollout.

A

After the new quay pod is passing its readiness checks, we can click on the status dot registry endpoint field to access the quay.

A

A

Remember we haven't begun using quay yet so we need to create a.

A

A

Let's push a simple image using our docker client to confirm everything is working.

A

We can see that the container we pushed appears in the quay ui now also notice that there is no security scan column because we disabled claire by marking it as unmanaged.

A

This has been a quick look at using unmanaged components with a quay container registry on openshift using the quay operator, thanks for watching.