GoogleCloudPlatform/kubernetes — pull request #569 by smarterclayton (2014-07-23 00:24:44+00:00)
Title: Kubelet etcd watch skipping indices

The next index to watch should always be current+1 if we got a
response from etcd, but otherwise it should always be current.
Moved the increment into fetchNextState which returns the next
index to watch for (or the same if an error occurs)

The kubelet will miss config changes in some cases without this
fix.