Min domains in PodTopologySpread

[sanposhiho]

Enhancement Description

• One-line enhancement description (can be used as a release note): support tuning the number of domains in PodTopologySpread
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3022-min-domains-in-pod-topology-spread
• Discussion Link:
  • Tuning the number of domains in PodTopologySpread kubernetes#105291
  • ( topologySpreadConstraint doesn't work fine when only one worker node is eligible for workload kubernetes#105072 )
• Primary contact (assignee): @sanposhiho
• Responsible SIGs: scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.24
  • Beta release target (x.y): 1.25
  • Stable release target (x.y): 1.30
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3022: Min domains in PodTopologySpread #3030
  • Code (k/k) update PR(s):
    • Add MinDomains API to TopologySpreadConstraints field kubernetes#107674
    • Implement MinDomains on Pod Topology Spread kubernetes#108362
  • Docs (k/website) update PR(s):
    • Document the new MinDomainsInPodTopologySpread feature gate website#32340
• Beta
  • KEP (k/enhancements) update PR(s): [KEP-3022] Write the production readiness requirements to graduate to beta #3338
  • Code (k/k) update PR(s): Graduate MinDomains in Pod Topology Spread to beta kubernetes#110388
  • Docs (k/website) update(s): Update the doc for minDomains to graduate minDomains to beta website#35202
• Stable
  • KEP (k/enhancements) update PR(s): KEP-3022: graduate Pod Topology Spread MinDomains to stable #4407
  • Code (k/k) update PR(s): graduate MinDomainsInPodTopologySpread to stable kubernetes#123481
  • Docs (k/website) update(s): graduate MinDomain feature to stable website#45180

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[sanposhiho]

/sig scheduling
/assign

[ahg-g]

/cc @x13n

[alculquicondor]

update the description to link to the merged KEP, instead of linking to the PR that added it.

[ahg-g]

/milestone v1.24

[Priyankasaggu11929]

Hello @sanposhiho 👋, 1.24 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022.

For note, This enhancement is targeting for stage alpha for 1.24 (correct me, if otherwise)

Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for this release
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.

With all the KEP requirements in place & merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

For note, the status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!