-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
quay-v3.9.1
-
False
-
-
False
-
-
Description:
This is an issue found in Quay 3.9.1 Operator, now in Quay 3.9.1 Quay add new storage option "maximum_chunk_size_gb" to AWS S3 Storage engine, but found after reconfigure Quay with Config Editor, this config was removed after operator reconcile the change, pls review this issue, see the attached Quay Operator POD logs quay391_operator_pod.logs
Quay: quay-operator-bundle-container-v3.9.1-7
Quay initial Deployment:
DISTRIBUTED_STORAGE_CONFIG: default: - S3Storage - host: s3.us-south.cloud-object-storage.appdomain.cloud maximum_chunk_size_gb: 2 port: "443" s3_access_key: ****** s3_bucket: quay3.3.0 s3_secret_key: ****** storage_path: /quay391ibmcos0905 DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS: - default DISTRIBUTED_STORAGE_PREFERENCE: - default
Quay config.yaml after using Config Editor to reconfigure Quay:
DISTRIBUTED_STORAGE_CONFIG: default: - S3Storage - host: s3.us-south.cloud-object-storage.appdomain.cloud port: "443" s3_access_key: ****** s3_bucket: quay3.3.0 s3_secret_key: ****** storage_path: /quay391ibmcos0905 DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS: - default DISTRIBUTED_STORAGE_PREFERENCE: - default