Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Multi-AZ topologies #78

Closed
benbromhead opened this issue Aug 3, 2018 · 2 comments
Closed

Multi-AZ topologies #78

benbromhead opened this issue Aug 3, 2018 · 2 comments
Assignees
@alourie

Comments

@benbromhead
Copy link
Collaborator

benbromhead commented Aug 3, 2018 •
edited
Loading

The behavior of Kubernetes scheduling pods across different failure domains is somewhat undefined and hard to control. See for details:

kubernetes/kubernetes#41598
kubernetes/kubernetes#44798
kubernetes/community#1857

Despite recent fixes to statefulsets, we still cannot inject failure domain information into the pods. So we still need to do a statefulset per failure domain.

This also gives us some flexability in tolerating outages and nodes being down in a single SS.
@eriksw
Copy link

eriksw commented Feb 21, 2019

Kubernetes 3.11 has been out for a while. Is there any update on this?

@alourie alourie self-assigned this Jul 11, 2019
@alourie
Copy link
Contributor

alourie commented Aug 22, 2019

Implemented with #192

@alourie alourie closed this as completed Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alourie alourie

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alourie @benbromhead @eriksw