Account for container images in billing and quotas

[larsks]

People are able to create container images in OpenShift via BuildConfig resources or by directly pushing images into the internal registry.

Container images can potentially consume a large chunk of storage. We should account for this in our billing and quotas. This will become particularly relevant as the amount of AI work on the clusters increases, since there are plans afoot to use container images as the mechanism for distributing AI models.

[larsks]

Here is the existing documentation on resource limits for images. It looks like we can limit:

• The maximum size of an individual image
• The total number of images in a namespace

But that's not the same thing as limiting the total amount of space consumed by images. I'll play with that a bit tomorrow to see if things work as expected.

[hpdempsey]

The decision about whether we want to bill for container image space is separate from investigating how much space we expect to need, how we can manage the space, and whether quotas are needed. It is possible that we choose only track the image space usage, rather than implementing all the mechanisms for billing and quotas, depending on the tradeoff between new development costs and the (very small) cost of storage.