fix(quay-docs):Adding changes to Addmaximum_chunk_size_gbStorage branch - #1797
Open
sarfarazgit wants to merge 1 commit into
Open
fix(quay-docs):Adding changes to Addmaximum_chunk_size_gbStorage branch#1797sarfarazgit wants to merge 1 commit into
sarfarazgit wants to merge 1 commit into
Conversation
Signed-off-by: Sarfaraz Ahamad <sarfarazzmca@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[Issue] This (maximum_chunk_size_gb) value controls the per-part size for S3 multipart uploads, and AWS S3 enforces a hard
limit of 5 GB per part. Setting it higher than 5 will cause S3 to reject the upload parts entityTooLarge).
chunk_size = maximum_chunk_size_gb if maximum_chunk_size_gb is not None else 5 # 5gb default
The issue is that the maximum_chunk_size_gb value is not currently documented in the Quay documentation, while the maximum_chunk_size_mb setting is already included in the referenced documentation.
The solution is to include maximum_chunk_size_gb in the referenced documentation to provide a more comprehensive description of the feature and improve the overall product documentation.
[Doc] https://docs.redhat.com/en/documentation/red_hat_quay/3.18/html/configure_red_hat_quay/config-fields-required-intro#config-fields-storage-noobaa