<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/jbeda/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/jbeda">@jbeda</a>'s idea.</p>
<p dir="auto">It might be useful to have our standard set up scripts have the master run a registry. This would make it easy to upload/distribute "local" images across the cluster.</p>
<p dir="auto">While Docker has a clear idea around local and remote images, with k8s we now have "cluster local" images that need to be distributed fast across the cluster but don't need to bounce off of the public registry.</p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):<br>
No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):</p>
<p dir="auto"><a href="https://github.com/kubernetes/kubernetes/issues?page=3&amp;q=is%3Aissue+is%3Aopen+loadbalancer+update&amp;utf8=%E2%9C%93">https://github.com/kubernetes/kubernetes/issues?page=3&amp;q=is%3Aissue+is%3Aopen+loadbalancer+update&amp;utf8=%E2%9C%93</a></p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):<br>
Bug report</p>
<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):<br>
Client 1.4.4<br>
Cluster 1.4.6</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: GKE</li>
<li><strong>OS</strong> (e.g. from /etc/os-release):</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>):</li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:<br>
3 node cluster</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
Apply a rolling update, see the new pods come up to Running and Ready, the old pod(s) terminate.<br>
Results in timeouts when hitting the load balancer. Wait a few minutes, and traffic is routed correctly.</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
Traffic is seamlessly routed to the new pods.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):<br>
<a href="https://gist.github.com/1d668ba12b12f450e8feffb21383ba44">https://gist.github.com/1d668ba12b12f450e8feffb21383ba44</a></p>
<p dir="auto"><code class="notranslate">kubectl apply -f deployment.yaml</code><br>
<code class="notranslate">kubectl get svc</code>, wait for the external IP to come up.<br>
Observe that traffic is routed correctly.</p>
<p dir="auto">Edit something (like the environment variable)<br>
<code class="notranslate">kubectl apply -f deployment.yaml</code><br>
Wait for old pods to be terminated. Observe timeouts until the load balancer updates itself.</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>