-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
Enabling/exposing chunksize for s3 storage driver
-
False
-
None
-
False
-
Not Selected
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
Release Note Not Required
Epic Goal
- Exposing the existing available chunksize configuration option the docker registry already supports.
- Fixing the multipart upload issues with Cloudflare R2 [ https://github.com/distribution/distribution/issues/3873 |https://github.com/distribution/distribution/issues/3873#issuecomment-1900164569]
Why is this important?
- Trying to use Cloudflare R2 as a storage backend. Small images where multipart isn't applied work fine, bigger images fail
- To enable multipart upload with greater chunksize
Scenarios
- Utilize the R2 cloudfare storage which requires higher chunksize
Acceptance Criteria
- New optional configuration option chunkSizeMiB
Dependencies (internal and external)
- None
Previous Work (Optional):
- https://github.com/openshift/cluster-image-registry-operator/pull/1026
- https://github.com/openshift/api/pull/1864
- https://github.com/openshift/api/pull/1877
Tested with:
- set registry operator unmanaged
- followed the doc https://docs.openshift.com/container-platform/4.15/registry/configuring_registry_stora[…]e/configuring-registry-storage-aws-user-infrastructure.html
- added env var to the deployment for chunksize
References::
https://docker-docs.uclv.cu/registry/storage-drivers/s3/
https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html
https://distribution.github.io/distribution/storage-drivers/s3/
- depends on
-
OCPBUGS-34678 HyperShift: OPERATOR_IMAGE_VERSION missing in cluster-image-registry-deployment
- Closed
- is related to
-
OCPBUGS-34399 Support chunksize feature via feature gate as TechPreviewNoUpgrade
- Closed
- links to
(10 links to)