Enhancements: DaemonSets should support MaxSurge to improve workload availability

Created on 2 Mar 2020  路  16Comments  路  Source: kubernetes/enhancements

Enhancement Description

  • One-line enhancement description: Many infrastructure components (CNI, CSI) require DaemonSets to place pods on each node, but the current update strategies limit end users from minimizing disruption during updates. It should be possible to surge daemonsets if a user requests it to allow handoff from one running pod to another, like Deployments.
  • Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/1591-daemonset-surge
  • Primary contact (assignee): @smarterclayton
  • Responsible SIGs: @kubernetes/sig-apps-feature-requests @kubernetes/sig-node-feature-requests
  • Enhancement target (which target equals to which milestone):

    • Alpha release target 1.20

    • Beta release target 1.21

    • Stable release target 1.23

kinfeature siapps sinode stagalpha trackeno

Most helpful comment

Giving timing I'm going to delay this to 1.21 since the impl needs more tests and I don't want to rush it.

All 16 comments

we need it for fluentd so that logs generated by our applications are still being picked up even when update is happening.

Hi @smarterclayton !

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:

The KEP PR must be merged in an implementable state
The KEP must have test plans
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

Please let me know and 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!

As a reminder, enhancements freeze is tomorrow May 19th EOD PST. In order to be included in 1.19 all KEPS must be implementable with graduation criteria and a test plan.

Thanks.

Unfortunately the deadline for the 1.19 Enhancement freeze has passed. For now this is being removed from the milestone and 1.19 tracking sheet. If there is a need to get this in, please file an enhancement exception.

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

/remove-lifecycle stale

Hi @smarterclayton

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

Hi @smarterclayton

Following up - any plans to start on this in 1.20? Enhancements Freeze is October 6th and the KEP is currently unmerged and provisional (it must be implementable).

Best,
Kirsten

Yes, KEP is ready for review for implementable, target would be alpha in 1.20 as denoted in KEP.

Hi @smarterclayton ,

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:

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

Regards,
Mikael

Hello @smarterclayton , 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 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!

Hi @smarterclayton
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:

Thank you!

Updated with docs placeholder.

Hey @smarterclayton

You're still intending on getting kubernetes/kubernetes#96375 in by tomorrow? Seems to just need a lgtm.

Thanks!
Kirsten

Giving timing I'm going to delay this to 1.21 since the impl needs more tests and I don't want to rush it.

@smarterclayton thanks for the update!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

robscott picture robscott  路  11Comments

dekkagaijin picture dekkagaijin  路  9Comments

mitar picture mitar  路  8Comments

boynux picture boynux  路  3Comments

xing-yang picture xing-yang  路  13Comments