Topology Aware Volume Scheduling

[msau42]

Feature Description

• One-line feature description (can be used as a release note): Make the scheduler aware of a Pod's volume's topology constraints, such as zone or node.
• Primary contact (assignee): @msau42
• Responsible SIGs: @kubernetes/sig-storage-feature-requests @kubernetes/sig-scheduling-feature-requests
• Design proposal link (community repo):Volume topology aware scheduling design community#1054, Add more details to volume scheduling design community#1168
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  • @jsafrane
  • @bsalamat
• Approver (likely from SIG/area to which feature belongs):
  • @thockin
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): 1.9
  • Beta release target (x.y): 1.10
  • Stable release target (x.y): 1.13

/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[msau42]

/remove-lifecycle-stale
/lifecycle frozen

I'm hoping to target beta in 1.10