ref/ kubernetes/kubernetes#57471

/cc

1. We had a long discussion about doing this here and decided not to. Is there a particular reason we should reconsider doing this now.
2. Features are closed for 1.10. Also, I don't see how you could reasonably release this as stable in 1.10.
3. We had the discussion in (1) prior to releasing DaemonSet to GA, is there a strong motivation to reconsider this now?
   /cc @janetkuo @bgrant0607

@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

• Feature target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y) 1.10

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.