Add a configurable default constraint to PodTopologySpread

[alculquicondor]

Enhancement Description

• One-line enhancement description: Add default spreading rules to pods that don't define one and allow operators to define it.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1258-default-pod-topology-spread
• Main repo issue: [Scheduler] Default spreading should be configurable for a topology kubernetes#80639
• Primary contact (assignee): @alculquicondor
• Responsible SIGs: sig-scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.19)
  • Beta release target (1.20)
  • Stable release target ()

[alculquicondor]

/sig scheduling

[mrbobbytables]

Hey there @alculquicondor -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.17?

Just a reminder that for it to be accepted -- the KEP must be merged, in an implementable state and have both a test plan and graduation criteria defined before the Enhancement Freeze.

The current release schedule is:

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

If you do think it'll make it, please let me know.

Thanks!

[alculquicondor]

Hi Bob. I believe I'll have it ready before the Enhancements Freeze.

/assign

[mrbobbytables]

great, thanks @alculquicondor I'll add it to the tracking sheet :)
/stage alpha
/milestone v1.17

[jeremyrickard]

Hey @alculquicondor, friendly reminder that enhancement freeze is quickly approaching (EOD PT, October 15th). Your KEP will need to be updated to the implementable state in order for us to include it in the release. It looks like it was merged, but is still listed as provisional.

[alculquicondor]

Thanks @jeremyrickard. We already have a PR to set that flag.

[jeremyrickard]

👍 great @alculquicondor.

[alculquicondor]

It's now marked as implementable.

[daminisatya]

Hello, @alculquicondor I'm 1.17 docs lead.

Does this enhancement (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

[alculquicondor]

Hello @daminisatya, these are the docs that need a few updates https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
https://kubernetes.io/docs/concepts/scheduling/kube-scheduler/

[daminisatya]

Thank you @alculquicondor Make sure you open a Docs PR against k/website (branch dev-1.17) due by Friday, November 8th.

[daminisatya]

Hello @alculquicondor

Just a friendly reminder, We're hoping to have a placeholder Docs PR against k/website (branch dev-1.17) by Friday, Nov 8th. (4 more days left)

[alculquicondor]

Done kubernetes/website#17409

[palnabarun]

Hi @alculquicondor

I am one of the Enhancements Shadow for the 1.17 Release Team. We are very near to the Code Freeze (Nov 14th) for this release cycle. Just checking in about the progress of this enhancement. I see that kubernetes/kubernetes#84606 was filed in relation to this. Is there any other PR related to this enhancement? If yes, can you please link them here?

Thank you in advance 😄

[alculquicondor]

1/2: kubernetes/kubernetes#84874

[palnabarun]

@alculquicondor Awesome! Thank you for the updates. :) Please let us know if and when 2/2 is filed.

[palnabarun]

Hi @alculquicondor , tomorrow is code freeze for the 1.17 release cycle. It looks like the k/k PR has not yet been merged. We're flagging as the enhancement as At Risk in the 1.17 Enhancement Tracking Sheet.

Do you think they will be merged by the EoD of the 14th (Thursday)? After that point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

[alculquicondor]

Hello @palnabarun even though the API changes got approved, we hit several blockers in the implementation. I don't think we can make it before the freeze. Could you please take it out of the release?

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alculquicondor]

/reopen

I'm gonna graduate this feature to GA in 1.24

[k8s-ci-robot]

@alculquicondor: Reopened this issue.

In response to this:

/reopen

I'm gonna graduate this feature to GA in 1.24

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alculquicondor]

/reopen

/help

[k8s-ci-robot]

@alculquicondor: Reopened this issue.

In response to this:

/reopen

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alculquicondor]

/remove-lifecycle rotten

[alculquicondor]

/assign @gavinfish

/remove help

[alculquicondor]

/remove-help

[kerthcet]

DefaultPodTopologySpread is GA in kubernetes/kubernetes#108278 already. Should we updated the description and whether any works remaining? @alculquicondor

[alculquicondor]

You need to update the state of the feature in the website https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#internal-default-constraints

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[alculquicondor]

Thanks @kerthcet for graduating this feature!

/close

[k8s-ci-robot]

@alculquicondor: Closing this issue.

In response to this:

Thanks @kerthcet for graduating this feature!

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.