Even pod spreading across failure domains

[bsalamat]

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.
• KEP: 20190221-pod-topology-spread.md
• Primary contact (assignee): @Huang-Wei
• Responsible SIGs: Scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target - 1.16
  • Beta release target - 1.18
  • Stable release target (x.y)

[kacole2]

@bsalamat I'm going to add this to the 1.15 milestone for tracking purposes. Once the KEP has been merged lets get the link updated. As usual, put any relevant k/k PRs to be tracked in this issue. Thanks!

/milestone v1.15
/stage alpha

[justaugustus]

/assign @Huang-Wei

[mrbobbytables]

@bsalamat, @Huang-Wei Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be in an "Implementable" state with proper test plans and graduation criteria. Please submit any PRs needed to make this KEP adhere to inclusion criteria. If this will slip from the 1.15 milestone, please let us know so we can make appropriate tracking changes.

[Huang-Wei]

@mrbobbytables thanks for the reminder.

@bsalamat I've raised #996 to address above concerns.

[daminisatya]

Hey, @Huang-Wei @bsalamat I'm the v1.15 docs release shadow.

I see that you are targeting the alpha version of this enhancement for the 1.15 release. Does this require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions! 😄