-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Topology Spread Constraints feature. #859
Support for Topology Spread Constraints feature. #859
Conversation
…y Spread constraints specification allows the pods to be spread across your cluster among multiple failure-domains.
This looks great, I'll test it and add some comments. Since this is a
|
Thanks, @dvaldivia !! Please let me know if I need to do anything else. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with k8s 1.17
and 1.21
. On 1.17
the topology gets removed from the statefulset but I didn't observe any re-sync of the statefulset from our operator, which might indicate either no problem, or no changes detected (which should happen)
@dvaldivia , Can you link this PR with the #666 issue? I cannot seem to assign this issue to myself and close it. |
This PR adds support for Topology Spread Constraints feature. The Topology Spread constraints specification allows the pods to be spread across your cluster among multiple failure-domains.
@nitisht