<p>I'm running the leader-elector (v0.5) as a sidecar on three pods, on three different nodes. </p>

<p>Arguments: --election=XXX --http=0.0.0.0:4040</p>

<p>All works well until I kill the leader pod. </p>

<p>Now I get one of the pods into a state where the logs say it switched to the new leader:</p>

<pre><code>kubectl logs -c elector upper-0
I0803 21:08:38.645849       7 leaderelection.go:296] lock is held by upper-1 and has not yet expired
</code></pre>

<p>So that indicates that <strong>upper-1</strong> is now the leader.</p>

<p>But if I do query the HTTP server of upper-0, it returns the old leader:</p>

<pre><code>kubectl exec -it upper-0 bash                                                        
root@nso-lsa-upper-0:/# curl http://localhost:4040                                                                                     
{"name":"upper-2"}
</code></pre>

<p>Do I need to do something for the leader-electors HTTP service to update?</p>

<p>It looks like a bug.<br>
There is an open issue on GitHub: <a href="https://github.com/kubernetes/contrib/issues/2930" rel="nofollow noreferrer">How is this possible? #2930</a></p>
