Support topologySpreadConstraints#306
Draft
brinkenberger wants to merge 1 commit intoweaviate:mainfrom
Draft
Conversation
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Secrets |  0  0  0  0 |
View in Orca |
|
To avoid any confusion in the future about your contribution to Weaviate, we work with a Contributor License Agreement. If you agree, you can simply add a comment to this PR that you agree with the CLA so that we can merge. |
Collaborator
|
@brinkenberger welcome! and thank you for your contribution I have a question: is your PR ready for review? |
Author
|
Hey, the PR can be closed. As mentioned in another issue, topologySpreadConstraints is not necessary, just use podAntiAffinity. If you want to continue on this PR, feel free to do so. |
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
3 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.
Currently it is not possible to distribute the deployment in different availability zones (AZ).
Say I have
replicas: 3and three zones:The following config can currently happen:
Replica 1: Node 1 / AZ1
Replica 2: Node 2 / AZ1
Replica 3: Node 3 / AZ2
I want the scheduler instead to prefer this config:
Replica 1: Node 1 / AZ1
Replica 2: Node 3 / AZ2
Replica 3: Node 5 / AZ3
By supporting topologySpreadConstraints, this is possible.