<p dir="auto"><a href="https://s3.amazonaws.com/archive.travis-ci.org/jobs/35977365/log.txt" rel="nofollow">https://s3.amazonaws.com/archive.travis-ci.org/jobs/35977365/log.txt</a></p>
<p dir="auto">Configurable, using labels to route traffic.</p>
<p dir="auto">From discussion: <a href="https://groups.google.com/d/msg/google-containers/frOLMyNl5U4/W5_DQUL933IJ" rel="nofollow">https://groups.google.com/d/msg/google-containers/frOLMyNl5U4/W5_DQUL933IJ</a></p>
<blockquote>
<blockquote>
<p dir="auto">I suppose, if we had some sort of dynamic router based on label queries, you could make that work for your needs with a bit of configuration. I'm not sure if there's really a need for that once DNS naming is set up, though.</p>
</blockquote>
<p dir="auto">I think you're going to want to incorporate some sort of http/s router or at least have a suggested means of configuring one. It seems to be one of the most obvious use cases for Kubernetes.</p>
</blockquote>
<p dir="auto">Like I said, I'm not sure this is needed if there's a good load balancer and DNS name resolution, but filing this for tracking the discussion.</p>