Enhancements: 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: kubernetes/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 https://github.com/kubernetes/kubernetes/pull/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 :smile:

[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?

[palnabarun]

Ah! Okay. Thank you for the updates. I am going ahead and removing the enhancement from this cycle.

We will look forward to having it in the next cycle.

[palnabarun]

/milestone clear

[jeremyrickard]

Hey there @alculquicondor,

1.18 Enhancements team here 👋

1.18 has kicked off this week, so I'm reaching out to see if you think this will make it into 1.18? Looks like you didn't make it to code freeze in the last cycle, any thoughts on that happening this time around? Looks like kubernetes/kubernetes#84874 is still open.

Let us know if you plan on introducing this as alpha in 1.18!

[alculquicondor]

Hello @jeremyrickard. We will indeed be working on this. The PR will need rework in the light of kubernetes/kubernetes#85737. Do you know when the release calendar will be posted?

[jeremyrickard]

@alculquicondor there is a PR with the calendar that hasn't quite merged yet, but the dates are:

v1.18 Start: January 6
Enhance Freeze: January 28
Code Freeze: March 5
Docs Ready: March 16
v1.18 Release: March 24

[jeremyrickard]

/milestone v1.18

[iheanyi1]

Hello @alculquicondor ,

I'm 1.18 docs shadow.

Just want to know if this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 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.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time.
Warm regards,

chima

[kikisdeliveryservice]

Hi @alculquicondor !

As a reminder that the Code Freeze is Thursday 5th March. Can you please link all the k/k PRs or any other PRs that should be tracked for this enhancement? So far I have https://github.com/kubernetes/kubernetes/pull/84874 for this Enhancement.

Thanks!
The 1.18 Enhancements Team

[iheanyi1]

Hello @alculquicondor ,

I'm 1.18 docs shadow.

Just want to know if this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 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.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time.

[alculquicondor]

Hello @kikisdeliveryservice, all my efforts are now directed towards #1451. I'll let you know when I have PRs for this.

@iheanyi1, here is the PR for docs kubernetes/website#19170

[sftim]

Following https://github.com/kubernetes/enhancements/issues/1258#issuecomment-587086972 it does look to me as if a few docs changes are needed, and there is indeed a placeholder PR open already.

[kikisdeliveryservice]

@alculquicondor Is this still targeted for 1.18? Code freeze is March 5th and PRs should be merged by then.

[alculquicondor]

kubernetes/kubernetes#88671 has the implementation of the feature and it's on review.

[alculquicondor]

kubernetes/kubernetes#88671 was merged.

In light of the performance results that we have today, in 1.18 we are not moving forward with replacing DefaultPodTopologySpread with PodTopologySpread+defaults, as described here https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20190926-default-even-pod-spreading.md#relationship-with-defaultpodtopologyspread-plugin

Other than documentation (kubernetes/website#19170) the work for this release should be considered done.

[harshanarayana]

Hey there @alculquicondor, 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[alculquicondor]

The KEP is already in place. I have to update the target to this release https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20190926-default-even-pod-spreading.md

[palnabarun]

/milestone clear

(removing this from the v1.18 milestone as that is complete)

[harshanarayana]

@alculquicondor Thank you for getting back to me with an update. I just went through the KEP and noticed that it is missing Graduation Criteria with regards to v1.19. Can you please update the same?

I will update the tracking sheet accordingly to consider this a valid entry into v1.19 👍

[alculquicondor]

We are going to alpha this release. We didn't make it in 1.18 https://github.com/kubernetes/enhancements/issues/1258#issuecomment-594026704

[harshanarayana]

@alculquicondor Thanks. I have updated the tracking sheet to reflect the same. Can you please ensure that the KEP also indicates that v1.19 is going to be alpha stage ? The KEP still shows Alpha (v1.18):. Thanks again. 👍

[palnabarun]

/stage alpha
/milestone v1.19

[harshanarayana]

Hey @alculquicondor, thank you for update the KEP Documentation for Graduation Criteria. Tracking sheet has been updated with the details.

Thanks again for your time and contributions. 🖖

[harshanarayana]

Hi @alculquicondor, member of Enhancements team for the v1.19 here with a quick update.

PR #1620 was merged recently, adding production readiness review questions to the KEP template. We are not making it mandatory for the 1.19 release cycle, but it would be great if the PRR questionnaire is filled in the KEP.

[divya-mohan0209]

Hello @alculquicondor , I'm one of the v1.19 docs shadows.

Could you please let me know if this piece of enhancement work planned for 1.19 release requires any new docs (or modifications to existing docs)?

If not, can you please update the 1.19 Enhancement Tracker Sheet (or let me know and I'll do so)

If yes, just a friendly reminder we're looking for a PR against k/website (branch dev-1.19) due by Friday, June 12, it can just be a placeholder PR at this time.

Please do let me know if you have any questions!

Regards,
Divya

[alculquicondor]

I will raise a PR to update https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/

[harshanarayana]

Hey @alculquicondor, I am with the enhancements team for the v1.19 release cycle as a shadow.

The code freeze deadline for the Enhancement is Thursday, June 25. I am checking in to see if there is any other k/k PR that you have outside of https://github.com/kubernetes/kubernetes/issues/80639 with regards to this enhancement and if so, would you be able to point me in the direction of the PR so that the same can be updated in the tracking sheet

Have a wonderful day. 🖖

[divya-mohan0209]

Hello @alculquicondor . Gentle reminder to update the Docs placeholder PR on this issue so that we can ensure it's tracked appropriately.

Thanks!

[harshanarayana]

Hi @alculquicondor, I am with the enhancements teams for the v1.19 cycle as the shadow.

I noticed that the PR kubernetes/kubernetes#91793 has been merged against the k/k. Is there any other PR you are anticipating for this enhancement in the v1.19 cycle that needs to be tracked?

Have a wonderful day. 🖖

[alculquicondor]

That's it for 1.19, other than docs.

[alculquicondor]

kubernetes/website#21689

[harshanarayana]

Hi, @alculquicondor

This probably not applicable to this enhancement as all the things for this are already in place. However, this is a follow-up to the communication that went out to k-dev today. There has been a revision to the release schedule of v1.19 as follows.

Thursday, July 9th: Week 13 - Code Freeze
Thursday, July 16th: Week 14 - Docs must be completed and reviewed
Tuesday, August 25th: Week 20 - Kubernetes v1.19.0 released
Thursday, August 27th: Week 20 - Release Retrospective

You can find the revised Schedule in the sig-release Repo

Please let me know if you have any questions. 🖖

[kikisdeliveryservice]

This graduated to alpha in 1.19. If you'd like to work towards beta in 1.20 please let us know.

/milestone clear

(removing this enhancement issue from the v1.19 milestone as the milestone is complete)

[alculquicondor]

We are graduating to beta for 1.20. I'll prepare a KEP update soon.

[kikisdeliveryservice]

Thanks @alculquicondor !

When you update the KEP can you also please fix the target and KEP link in the description?

/milestone v1.20

[alculquicondor]

/retitle Add a configurable default constraint to PodTopologySpread

[MorrisLaw]

Hey @alculquicondor -- 1.20 Enhancements Shadow here 👋

I see that a PR with changes to a KEP is still in flight. Just a friendly reminder that the Enhancements Freeze deadline is October 6th. Otherwise, an exception will need to be submitted.

Appreciate the work!

Regards,
Jeremy

[MorrisLaw]

Hey @alculquicondor 👋

Just a reminder that the changes to this KEP will need to be in by the October 6th Enhancements freeze deadline if we want to graduate to beta in 1.20.

Regards,
Jeremy

[alculquicondor]

graduation to Beta was just approved, thanks :)

[MorrisLaw]

Hi @alculquicondor ,

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Best,
Jeremy

[reylejano-rxm]

Hello @alculquicondor , 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against the dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th.

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[reylejano-rxm]

Hi @alculquicondor

The docs placeholder deadline is almost here. Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline

Also, please keep in mind the important upcoming dates:

• Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

[alculquicondor]

All tasks for 1.20 are completed