add s3 minimum part size support #645
Open
+58
−0
Conversation
This file contains 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
Signed-off-by: Renan Rangel <rrangel@slack-corp.com>
5 tasks
Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
frouioui
approved these changes
Dec 14, 2024
There was a problem hiding this comment.
This looks good for me, I have pushed c999a42 which re-generates the CRDs, the documentation, and the operator-latest.yaml.
Please note that the changes made to operator-latest.yaml should be ported over to your PR on vitess (vitessio/vitess#17171) into the file ./examples/operator/operator.yaml.
mattlord
approved these changes
Dec 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR complements vitessio/vitess#17171 to add support for setting the minimum S3 part size via the
vitess-operatoras well.