<p dir="auto">It appears that kube-ui supports only 'default' namespace.<br>
Any pod,rc,service created in namespaces other than 'default' are not shown/accessible via kube-ui.</p>
<p dir="auto">While debugging <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="59921304" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/5091" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/5091/hovercard" href="https://github.com/kubernetes/kubernetes/issues/5091">#5091</a> I noticed that when I'm creating guestbook application by running <code class="notranslate">./cluster/kubectl.sh create -f examples/guestbook</code> there is a chance that frontend pods come up before information about environment variables of redis is propagated. In such case frontend can't connect to database during its whole life.</p>
<p dir="auto">It's actually more general problem, since most of complex application might be affected by this. Also I think create a set of resource (especially by specifying the directory of their config files) should just work no matter of the order of creation.</p>
<p dir="auto">I can see few solutions of such problem:</p>
<ol dir="auto">
<li>Get rid off HOST:PORT stuff and start using DNS service instead.</li>
<li>Add ability to wait for such information being propagated.</li>
<li>Injecting environment variables to container somehow(?).</li>
</ol>