-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schedule DaemonSet Pods by kube-scheduler #548
Comments
/cc |
|
@kow3ns There has been more discussions and the SIG scheduling has decided to go in this direction. @bgrant0607 has been in the loop in the discussions. Please refer to this doc for more details: https://docs.google.com/document/d/1v7hsusMaeImQrOagktQb40ePbK6Jxp1hzgFB9OZa_ew/edit |
From kubernetes/kubernetes#59630 this feature should be alpha, instead of stable. And if this targets 1.10, it needs to be added to 1.10 milestone. Also, have any of you filed exception request for this feature? |
@jberkus the exception is filed here: https://groups.google.com/forum/#!topic/kubernetes-milestone-burndown/sPvjpRMf5es Adding to v1.10 milestone to get attention from release team. |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Task 2: Schedule DaemonSet Pods by default scheduler. Signed-off-by: Da K. Ma <[email protected]> **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: part of #59194 kubernetes/enhancements#548 **Release note**: ```release-note When ScheduleDaemonSetPods is enabled, the DaemonSet controller will delegate Pods scheduling to default scheduler. ```
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. disable DaemonSet scheduling feature for 1.10 The DaemonSet scheduling feature has blocked the alpha CI job being green and is preventing getting good CI signal for v1.10 It still contains pod scheduling races (#61050) and fundamental issues with the affinity terms it creates (#61410) As such, there is not significant value in having the feature available in 1.10 in the current state This PR disables the feature in order to regain green signal on the alpha CI job (reverting commits is likely to be more disruptive at this point) related to #61050 ```release-note DaemonSet scheduling associated with the alpha ScheduleDaemonSetPods feature flag has been removed from the 1.10 release. See kubernetes/enhancements#548 for feature status. ```
…1-upstream-release-1.10 Automatic merge from submit-queue. Automated cherry pick of #61411: disable DaemonSet scheduling feature for 1.10 Cherry pick of #61411 on release-1.10. related to #61050 #61411: disable DaemonSet scheduling feature for 1.10 ```release-note DaemonSet scheduling associated with the alpha ScheduleDaemonSetPods feature flag has been removed from the 1.10 release. See kubernetes/enhancements#548 for feature status. ```
@k82cn If so, can you please ensure the feature is up-to-date with the appropriate:
cc @idvoretskyi |
/stage alpha |
Thanks for the update, @k82cn! |
@k82cn please fill out the appropriate line item of the |
Doc for 1.11: kubernetes/website#8842 |
@justaugustus @idvoretskyi apparently this feature went in for 1.10 and it's just that it was missing docs until now. So I don't think it should be considered a 1.11 feature. Is that correct? At least the docs submitted in the linked docs PR only mention "1.10 and higher" several times. |
@MistyHacks , that should be 1.11; part of this feature are merged in 1.10 (which is considered as separate part), so I mark them 1.10 :). |
Oh, ok. Thanks for the clarification. |
@k82cn we need to change feature gate comment of this to 1.11 (instead of 1.10): |
Hello @k82cn , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly. |
Hi @k82cn - I'm an Enhancements shadow for 1.16. 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. Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly. I noticed there's no KEP linked in the issue description; as a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements. As a reminder, 1.16 milestone dates are: Enhancement Freeze 7/30 and Code Freeze 8/29. Thanks! |
we'd like to promote this feature to GA in 1.17 :) |
👋 hey there @k82cn -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to stable in 1.17? The current release schedule is:
If you do, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍 Thanks! |
Hi @k82cn , -- 1.17 enhancements shadow here. Just a friendly reminder. We are just 5 days away from the Enhancements Freeze. For the KEP to be considered for 1.17,
|
ack :) |
Looking over the KEP, the test plan references tests for Thanks! |
@draveness @k82cn - release lead here. Overall, this graduation seems to be very much in line with reality and experience, we just want a bit more visibility to detail. I'd also second the request for more elaboration in kubernetes/kubernetes#83829. |
I'll update the KEP
Sure |
Hello @k82cn I'm one of the v1.17 docs shadows. 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! |
Since we're approaching Docs placeholder PR deadline on Nov 8th. Please try to get one in against k/website dev-1.17 branch. |
The document PR is here kubernetes/website#17350 |
Hey there @draveness -- 1.17 Enhancements lead here. I just wanted to check back in regarding the upcoming code freeze on November 14th. It looks like just about everything is done going by the list in kubernetes/kubernetes#82702. Do you know if the last outstanding issue ("Refactor nodeShouldRunDaemonPod to remove useless return values") will make be merged in time? |
"Refactor nodeShouldRunDaemonPod to remove useless return values" is optional to me, it's just code refactor, no behaviour change :) |
Hey @draveness @k82cn, Happy New Year! 1.18 Enhancements lead here 👋 Thanks for getting this across the line in 1.17!! I'm going though and doing some cleanup for the milestone and checking on things that graduated in the last release. Since this graduated to GA in 1.17, I'd like to close this issue out but the KEP is still marked as implementable. Could you submit a PR to update the KEP to implemented and then we can close this issue out? Thanks so much! |
We could close this issue since this is already GA'ed /close |
@draveness: Closing this issue. In response to this:
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. |
@draveness yes, I was just asking if you could update the status of the KEP :) It's still marked as |
Thanks, I've opened #1437 to mark it as implemented |
Feature Description
The text was updated successfully, but these errors were encountered: