<p dir="auto">As discussed <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="60182440" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/5156" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/5156/hovercard" href="https://github.com/kubernetes/kubernetes/issues/5156">#5156</a> and in other places, the load balancer creation should not be synchronous with resource creation (goes against the "dumb resources" model) but instead be applied by a controller both before and after creation.</p>
<p dir="auto">I'm trying to bring up a service and pod (<a href="https://github.com/youtube/vitess/examples/kubernetes/vtctld-up.sh">https://github.com/youtube/vitess/examples/kubernetes/vtctld-up.sh</a>).  The service has createExternalLoadBalancer: true.  The call nearly always returns:<br>
ERROR: F0306 15:59:47.443762   17632 create.go:81] Timeout: request did not complete within allowed duration.</p>
<p dir="auto">I then proceed to create a firewall rule (created successfully) and access the service, which occasionally works.  Note the non-determinism:</p>
<ol dir="auto">
<li>I nearly always get the timeout error (&gt; 90%).</li>
<li>Even if I get the timeout error, I can still create the firewall rule and it's a toss-up whether I can access the service or not.</li>
<li>If I automate these steps in a script (bring up cluster, bring up service, create firewall rule), I am virtually never able to access the service using the forwarded IP and port.</li>
</ol>
<p dir="auto">Our thoughts are that adding the external load balancer makes bringing up the service take longer, putting it at risk of timeout.  I couldn't find a way to increase the timeout threshold in kubectl create.</p>
<p dir="auto">In addition there may be some hidden steps or waits between steps that are needed since the automation never works, but running the steps manually sometimes does.</p>
<p dir="auto">Also of note is that this seems to be new behavior.  Prior to 3/5/2015, I hadn't seen any issues (if the timeout error occurred, it didn't have any impact), automation worked completely fine.</p>