Red Hat OpenShift Quay | OpenShift, 23 May 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Red Hat Quay Storage Quota Demo

Description

In this demo we will show you how storage quotas in Red Hat Quay help effectively control and contain growth in a central multi-tenant container registry.

This is one of the new features of Red hat Quay 3.7. Be sure to also check out the other new features in our launch blog post: http://content.cloud.redhat.com/blog/red-hat-quay-3.7-introduces-caching-storage-quotas-more

A

Hello, this is a demo of the new storage quota management functionality introduced in redheadquave 3.7.

A

My name is dania messer, I'm the product manager for redheadquay, and I'm going to take you on a quick tour through this new management capability, but first things. First, since quota management is a brand new feature, we do not enable it by default for existing quake configurations, make sure you have the feature flag for coder management enabled in the quake configuration file like shown here.

A

With this prerequisite, jacked off, let's head to the quay ui, you will notice that in the repository list view there is a new column that shows the storage consumption of each of the repositories this user currently has access to.

A

When we look at one of the organizations this user is a member of, we can also see the total aggregate storage consumption of all the image repositories inside this organization.

A

Each repository is also tracking its own storage utilization, which is defined as the sum of all image tags inside the respective repository.

A

In the tag list view you can see the individual image sizes, this information lets you quickly drill down into an organization and identify where the store's consumption originates from. Let's put some additional content into the registry, I'm going to use scorpio to conveniently copy images from a public registry into the organization we just looked at.

A

When we switch back to the query, ui and refresh, we can see that both the consumption of the repository I pushed the tag into as well as the total organization. Consumption were updated immediately right now, I can store as much as I want in my test organization.

A

Let's change that by applying a quota in the repository list tool, you may already have spotted that some repositories report their consumption along with a percentage value. This is because they are part of an organization that has a storage quota set. We are going to do the same now for our organization.

A

Storage quotas in quay are applied at the organization level. The persona that can set, modify or disable quotas in grey is the super user.

A

I am currently logged in as a super user and can switch perspectives by going to the admin panel in the organization list view, I can see all organizations that are currently created in my environment, including total storage consumption for the entire registry storage, utilization of each individual organization and percentage of quota used if one is defined.

A

This is very useful to identify large consumers in the system. Let's set a quota for my test organization.

A

First I'll set the overall storage quota for this organization, one gigabyte for now after I applied that I can now define a quota policy.

A

This allows me to define what happens when a certain threshold barrier is reached first I'll define that the organization should reject any new content getting pushed when the quota attainment reaches 100 percent or one gigabyte. In this case, then I'll set an additional threshold at 80 quarter, attainment or 800 megabytes in this case to start generating warnings for the organization owners.

A

This kind of policy lets tenants of the registry know when they are about to reach a certain storage utilization and will then enforce a hard cap at the quota limit. Let's see how that works from the user perspective, the organization is currently at roughly 75 utilization.

A

I'm going to push additional images first I'll copy the query builder image into my registry. This should not exceed the quota for now, as the image is roughly 150 megabytes.

A

As a result, I am now at 91 utilization and, as expected, the system starts to warn me that I am nearing my capacity limit.

A

To introspect my quota configuration and the various threshold definitions as a user, I can look at this in my organization's settings panel notice that, since only the superuser persona can adjust coders in the systems, these settings are read only for me.

A

Let's push some more content. The query image of the project quay open source project is roughly 350 megabytes and will definitely not fit my remaining storage capacity. Let's push it to see what happens as you can see. The upload fails halfway through because I'm exceeding my quota.

A

If we go back to the quayui, we can also see that, while the repository for the query image has been created, the image tag has not been uploaded and my utilization remains at 91.

A

Now that I have effectively reached my limit, I need to interact with the registry administrator to increase it. This way query administrators can contain and control growth in a multi-tenant environment.

A

Since I am already logged in as the super user, I can increase the quota for this particular organization right away. Heading back to the settings panel, I can update a quota and set it to 2 gigabytes.

A

Alternatively, I could have lifted the reject policy at the 100 quota utilization. This is useful in emergency situations when you do not want to increase the quota for a project long term, but you want to unblock them short term attempting to push the query image again. Now succeeds. Thanks to my expanded storage limit.

A

While, as a quay administrator, you can individually manage organization quota, like I have just shown, you may want to define a registry-wide default. This default quota is applied to every newly created organization and every existing organization that doesn't already have a quota configured in my environment. I have several of those cases.

A

To set the system by default coder, I add the corresponding setting to my query configuration file. The value for the field is specified in bytes and I am setting it here to 10 gigabytes.

A

Then I need to restart quay.

A

Once that is done, we will see that all organizations that previously didn't have a quota defined are now limited to 10 gigabyte. The default coder has also a policy attached that rejects any new content at 100 utilization.

A

If I create a new organization, I will immediately see that it is subject to the default quota from here on. I need to justify to the holder of the quaysuperuser privilege why I need more than that. This way, the default quota is an additional instrument to keep registry growth in check when new projects and tenants are onboarded.

A

This concludes this demonstration be also sure to check out the other new features of redhead quay 37, pull through caching container native, fills and geo-replication with the redhead quay operator. Thanks for watching.

A