Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-5467

Dont rely on default storage classes for Quay managed deployments

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Quay
    • None
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

      Currently, quay deployments onto openshift using the operator use the default storage class for quay and clair, and the default ObjectStorage class for s3 object storage.

      In a cluster with lots of different storage classes, this might lead to selecting a wrong storage classes. Switch the default storage class before/after deployment is an ugly workaround that can be dangerous and does not work will in gitops/IaaC type of operators of the cluster. Background: cluster has plenty of storage classes, ranging from cheap/slow NFS via NAS, ODF or SAN storage. All of those have different attributes in regards to speed, price, availability etc. Esp. for quay, I want to be able to choose that wisely.

      As OpenShift admin, I want to be able to specify the storage classt that is is used by managed quay components like quay, clair etc. so that I am in control of the config and select the best suitable storage out of the plenty of options my on prem datacenter cluster has in regards to storage.

            DanielMesser Daniel Messer
            dfroehli42rh Daniel Fröhlich
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: