Red Hat OpenShift Quay SIG | OpenShift Commons, 18 Dec 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Quay Operator Setup

Description

Quay Operator Setup
Simplifing the Installation and Configuration of Red Hat Quay on OpenShift

Additional Resources:

https://github.com/redhat-cop/quay-operator
https://projectquay.io

A

This is a demonstration of the quays setup operator, an operator to simplify the installation and configuration of red head Quay on open shift.

A

The quasi setup operator was created and managed in collaboration with the container community of practice within red hat and a red hat engineering, and the functionality of the operator is to automate the initial deployment of Red Hat, Quay and Claire, and also configure all the relevant open, shipped objects that are part of the Quade ecosystem, including routes secrets and deployments.

A

Some of the other capabilities that are available within the Quay setup operator is to deploy and manage a separate, Postgres sequel database within the name namespace or to leverage an existing one for usage by Red, Hat, Quay and Claire.

A

It also allows you to provide custom certificates for both Quay and Claire to ensure secure communication, as well as the ability to leverage different storage backends, either through local directory mounts or as required, in a production step through object storage, as well as creating externalized routes, with an open shift to an extent to enable access to the user, interface and back-end storage for our demo. Today, we're going to showcase how to deploy and see the integration between Red, Hat, Quay and Claire, using only a few steps to streamline the process.

A

So we have an open shift cluster here. Our first step is to go in and create a new namespace. Let's go ahead and call it create Enterprise.

A

We can also give it a name we'll call it high enterprise as well, and click create.

A

Once we have a new project created, we must then create a image, pull secret. That has our credentials to authenticate and retrieve images from Cueto. Let's go ahead and create that image pull secret.

A

With our image, pull secret now created within our project, let's go over to operator hub and go ahead and retrieve the quays operator.

A

We can go in in filter by quite.

A

Click on continue and click install.

A

When creating the subscription go ahead and subscribe and the operator will be deployed into the current namespace.

A

Let's go ahead and click on quite and then click on a Quay ecosystem resource. We then go in and click on, create query Co system.

A

By default, you're, given a very simplistic example for which you can deploy Quay, since, if you also want to deploy Claire, let's go ahead and modify the quay. Echo system object. As you see here, we've added a little bit more to our spec, we're specifying that we want to deploy Quay and utilize. The Red Hat pull secret that we created in a prior step.

A

We also want to enable Claire and also once again use that same pole secret, since we did not specify a database, one will be automatically deployed as part of this deployment of the ecosystem and we'll go ahead and put that and create.

A

It will take a few minutes for all of the components to be downloaded and installed into this project.

A

With Quay now deployed, let's go ahead and assess the Quay interface, we'll go in and select the route that was created and then log in.

A

Let's go ahead and create a new repository for an image that we're going to push to Quay we're going to go ahead and deploy the universal base. Image version 7, so ubi 7 is what we'll call it will create the repository we can then use the scope, yo command to go in and deploy or pardon me copy. The registry or the image to the registry.

A

With the image now pushed successfully, let's refresh the page go to our tags, we'll see. We now have a new tag called latest. We are going to give it a moment and in a second, our security scan over here will go in and complete. This is Claire going in and scanning our image for any vulnerabilities.

A

As you can see, our security scan has passed. If we go in and see that no vulnerabilities are found, we can see all the different packages that are part of this image and see that there are no current vulnerabilities, ensuring we are utilizing a secure image for all of the users who are leveraging our image.

A

In conclusion, this was a brief demonstration of the Quai setup operator for additional information regarding all the available options. The operative supports. Please take a look at the documentation. Thank you.