Enhancements: 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! 😄

[daminisatya]

@Huang-Wei @bsalamat

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! 😄

[mrbobbytables]

@Huang-Wei @bsalamat. Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

If you know this will slip, please reply back and let us know. Thanks!

[mrbobbytables]

@Huang-Wei @bsalamat, today is code freeze for the 1.15 release cycle. I do not see a reply for any k/k PRs to track for this merge. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. If there is no response, or you respond with PRs to track and they are not merged by EOD PST, this will be dropped from the 1.15 Milestone. After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

[kacole2]

/milestone clear

[kacole2]

Hi @bsalamat @Huang-Wei , I'm the 1.16 Enhancement Lead. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[Huang-Wei]

@kacole2 Yes, it's on the right track for 1.16, and it will be an Alpha feature.

[daminisatya]

@bsalamat @Huang-Wei

I'm one of the v1.16 docs shadows.
Does this enhancement (or the work planned for v1.16) require any new docs (or modifications to existing docs)? If not, can you please update the 1.16 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.16) due by Friday, August 23rd, it can just be a placeholder PR at this time. Let me know if you have any questions!

[Huang-Wei]

@daminisatya It needs new docs. The doc PR (placeholder atm) has been created - https://github.com/kubernetes/website/pull/15514

[kacole2]

@Huang-Wei @bsalamat code freeze for 1.16 is on Thursday 8/29. Are there any outstanding k/k PRs that still need to be merged for this to go Alpha? It looks like everything at https://github.com/kubernetes/kubernetes/issues/77284 has been merged

[Huang-Wei]

@kacole2 All code changes have been merged. So we're good.

The only left one is the document PR. Do you happen to know the timeline for documentation?

[kacole2]

@Huang-Wei
Docs deadline - PRs ready for review 9/3 (TODAY)
Docs complete - All PRs reviewed and ready to merge 9/9

[mrbobbytables]

Hey there @bsalamat @Huang-Wei -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to alpha/beta/stable in 1.17?

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, please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

/milestone clear

[Huang-Wei]

@mrbobbytables We will let it stay in Alpha in 1.17. So no status change in 1.17.

[mrbobbytables]

Noted. Thanks for being quick to respond!

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

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

[Huang-Wei]

/remove-lifecycle stale

[palnabarun]

Hey there @bsalamat @Huang-Wei -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to beta in 1.18 or having a major change in its current level?

The current release schedule is:

• Monday, January 6th - Release Cycle Begins
• Tuesday, January 28th EOD PST - Enhancements Freeze
• Thursday, March 5th, EOD PST - Code Freeze
• Monday, March 16th - Docs must be completed and reviewed
• Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release,

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

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements

Thanks! :)

[Huang-Wei]

@palnabarun Thanks for the reminder. After discussion with the SIG, we're going to promote this to beta in 1.18. Will send out a PR to update the KEP.

[palnabarun]

@Huang-Wei That's sounds awesome. Please note that the KEP is lacking Graduation Criteria for Beta.

Please note that they should be updated before the enhancements freeze on Tuesday, January 28th, failing which an exception would be needed.

[palnabarun]

/stage beta

[palnabarun]

/milestone v1.18

[palnabarun]

@Huang-Wei I see that the PR to update the KEP was merged. Also, the issue description has an outdated KEP link now. If https://github.com/Huang-Wei/enhancements/blob/master/keps/sig-scheduling/20190221-pod-topology-spread.md is the correct one, shall I go ahead and updated the issue description?

[ahg-g]

Here is the merged KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20190221-pod-topology-spread.md

[Huang-Wei]

@palnabarun Ah, please help to update the KEP link to https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20190221-pod-topology-spread.md. Thanks!

[palnabarun]

Updating it.

[savitharaghunathan]

Hello, @Huang-Wei ! I'm 1.18 docs shadow. Does 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. Let me know if you have any questions!

Thanks,
Savitha

[Huang-Wei]

@savitharaghunathan I created a placeholder PR here https://github.com/kubernetes/website/pull/18969

[palnabarun]

Hi @Huang-Wei, just a friendly reminder that the Code Freeze will go into effect on Thursday 5th March.

Can you please link all the k/k PRs or any other PRs which should be tracked for this enhancement?

Thank You :)

[Huang-Wei]

@palnabarun Here is an umbrella issue (https://github.com/kubernetes/kubernetes/issues/87662) tracking the PRs. It progresses well right now - an e2e PR and a document PR need to be finished.

[palnabarun]

Thank you @Huang-Wei for the updates. It's great to see the progress. :)

[Huang-Wei]

@palnabarun All items to qualify this feature to be beta in 1.18 has been completed. Feel free to update the description of this issue.

[palnabarun]

Thanks @Huang-Wei for the efforts. :clap:

I will update the issue comment.

[palnabarun]

/milestone clear

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

[Huang-Wei]

@palnabarun we'd like to promote it to GA in 1.19.

[palnabarun]

Hi @Huang-Wei, thank you for the update. We will update the tracking sheet accordingly. :+1:

[palnabarun]

/stage stable
/milestone v1.19

[Huang-Wei]

1796 is just adopting the new KEP template (with PRR).

[divya-mohan0209]

Hey, @Huang-Wei @bsalamat I'm one of the v1.19 docs release shadows.

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

If not, can you please update the 1.19 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.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

Regards,
Divya

[Huang-Wei]

@divya-mohan0209 https://github.com/kubernetes/website/pull/21115 acts as a placeholder.

[kikisdeliveryservice]

Hi @Huang-Wei Just to confirm: is this now code complete for 1.19 GA?

[Huang-Wei]

@kikisdeliveryservice yes, all code items have been completed - tracked at https://github.com/kubernetes/kubernetes/issues/89433#issuecomment-606827765.

[kikisdeliveryservice]

Hi @Huang-Wei !

Thanks for letting me know! This is mostly not applicable as your code is complete, but to follow-up on the email sent to k-dev today, I wanted to let you know that Code Freeze has been extended to Thursday, July 9th. You can see the revised schedule here: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.19

Please let me know if you have any questions. 😄

Best,
Kirsten

[kikisdeliveryservice]

Hi all

Enhancements Lead here. As this graduated to stable in 1.19 and the underlying KEP is marked implemented I am closing this issue.

Thank you for all of your work!!

Best,
Kirsten