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.

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

Even pod spreading across failure domains #895

bsalamat opened this Issue Mar 14, 2019 · 0 comments


None yet
2 participants
Copy link

bsalamat commented Mar 14, 2019

Enhancement Description

  • One-line enhancement description (can be used as a release note): This feature enables Kubernetes scheduler to spread a group of pods across failure domains. The existing hard inter-pod anti-affinity does not allow more than one pod to exist in a failure domain. The new feature supports more than one pod in a failure domain.
  • Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR)
  • Primary contact (assignee): @Huang-Wei
  • Responsible SIGs: Scheduling
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y) 1.15
    • Beta release target (x.y)
    • Stable release target (x.y)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.