[DPE-4946] S3 integrations cluster #287
Merged
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
Co-authored-by: Mehdi Bendriss <[email protected]>
Co-authored-by: Mehdi Bendriss <[email protected]>
MiaAltieri
changed the title
MiaAltieri
force-pushed
the
s3-integrations-cluster
branch
from
db30584
to
695283f
Compare
Gu1nness
approved these changes
Aug 1, 2024
Mehdi-Bendriss
approved these changes
Aug 2, 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.
Info
Following the star toplogy design on large deployments / sharding, we need to ensure that the s3 integrator is only related to the Config server
i.e. Relations to s3 integrator or only possible via config-server + replica deployments
In theory this should be feasible should be feasibly with the libs that we re-use from Charmed MongoDB VM so we added a test to verify