In PodConfigNotificationIncremental PodConfig mode, when no pods are available
for a source, the Merge function correctly concluded that neither ADD, UPDATE nor
REMOVE updates are to be sent to the kubelet. But as a consequence the kubelet will
not mark that source as seen.

This is usually not a problem for the apiserver source. But it is a problem for
an empty "file" source, e.g. by passing an empty directory to the kubelet for
static pods. Then the file source will never be seen and the kubelet will stay
in its special not-all-source-seen mode.

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

This avoid that we either waste cpu resources due to rounding or that we report
to much to the kubelet such that the e2e tests think they can schedule more than
resources are available.

This fixes https://github.com/mesosphere/kubernetes-mesos/issues/437

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

- simplify
- rename kubeletExecutor -> executorKubelet
- move executorKubelet code into kubelet.go
- remove duplicated executorKubelet.ListenAndServe
- fix executorKubelet.Run comment

This patch reduces the dependencies of the executor from the kubelet. This
makes it possible launch the kubelet after the executor.

This considerably reduces the complexity of the startup code.

Moreover, this work is a requirement to use a standalone kubelet some day.

MESOS: Update mesos/docker cluster docker images

Rename e2e-gce-release job to e2e-gce-release-1.0

Auto commit by PR queue bot

Use [Conformance] to tag conformance tests