We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

[Copying comment from @bgrant0607 in #14326, for posterity]

Re. evolution of this API:

Before DaemonSet graduates from experimental, it needs to adopt the more general selector, as discussed in #341. This would be very hard to change later.

Before DaemonSet reaches v1beta1, I'd like to see:

Rolling update as a service, similar in spirit to Deployment (#1743). For now, pod template updates are forbidden. However, DaemonSet should be declarative and should perform rollouts when its template is modified. I envision DaemonSet creating PodTemplate resources behind the scenes instead of ReplicationController resources.
Before DaemonSet reaches v1, I'd like to see:

Either integration into the node controller in order to integrate with node lifecycle, such as creation before other pods can be scheduled and implicit forgiveness behavior (#1574), or use of initializers and finalizers (#3585) to achieve the same
The created-by annotation replaced with controllerRef, as proposed in #2210
Cascading deletion implemented using an existence dependency, as proposed in #1535

GCE e2e build/test passed for commit 6ec362b.

• Build Log
• Test Artifacts
• Internal Jenkins Results

GCE e2e build/test passed for commit 0cb5553.

• Build Log
• Test Artifacts
• Internal Jenkins Results