Add configurable topologySpreadConstraints for Trino gateway deployment #336
Conversation
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
Member
Author
|
Hmm, not sure why the nodeport test fails. Doesn't seem relevant to this change. Any ideas ? |
Member
|
It's known to be flaky, I've retried it. |
Member
Author
|
Thanks a lot! it passed now |
nineinchnick
reviewed
May 3, 2025
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.
Allow topologySpreadConstraints to be configurable for the Trino gateway deployment.
A common usecase for this would be ensuring that pods are available in multiple AZ to make the Trino gateway deployment more resilient to single AZ failures.