<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">generated.Asset</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):</p>
<p dir="auto">Bug Report</p>
<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<p dir="auto">Today's HOT.</p>
<p dir="auto">commit <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/kubernetes/kubernetes/commit/b71def750f3ec1978b0e890e6fae106a20f33a9b/hovercard" href="https://github.com/kubernetes/kubernetes/commit/b71def750f3ec1978b0e890e6fae106a20f33a9b"><tt>b71def7</tt></a></p>
<p dir="auto"><strong>Environment</strong>:</p>
<p dir="auto">Build on Ubuntu 16.04</p>
<p dir="auto"><strong>What happened</strong>:</p>
<p dir="auto">git pull of latest code, then make release fails with</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="+++ [0930 02:04:05] Starting etcd instance
etcd --advertise-client-urls http://127.0.0.1:2379 --data-dir /tmp.k8s/tmp.fcfyJnEiqq --listen-client-urls http://127.0.0.1:2379 --debug &gt; &quot;/dev/null&quot; 2&gt;/dev/null
Waiting for etcd to come up.
+++ [0930 02:04:05] On try 1, etcd: :
{&quot;action&quot;:&quot;set&quot;,&quot;node&quot;:{&quot;key&quot;:&quot;/_test&quot;,&quot;value&quot;:&quot;&quot;,&quot;modifiedIndex&quot;:3,&quot;createdIndex&quot;:3}}
+++ [0930 02:04:06] Running integration test cases
Running tests for APIVersion: v1,apps/v1alpha1,authentication.k8s.io/v1beta1,authorization.k8s.io/v1beta1,autoscaling/v1,batch/v1,batch/v2alpha1,certificates.k8s.io/v1alpha1,
extensions/v1beta1,imagepolicy.k8s.io/v1alpha1,policy/v1alpha1,rbac.authorization.k8s.io/v1alpha1,storage.k8s.io/v1beta1
+++ [0930 02:04:07] Running tests without code coverage
# k8s.io/kubernetes/test/e2e/framework
test/e2e/framework/gobindata_util.go:30: undefined: generated.Asset
test/e2e/framework/gobindata_util.go:33: undefined: generated.AssetNames
Makefile:118: recipe for target 'test' failed
make[1]: *** [test] Error 1
+++ [0930 02:05:19] Cleaning up etcd
+++ [0930 02:05:19] Integration test cleanup complete
Makefile:130: recipe for target 'test-integration' failed
make: *** [test-integration] Error 1
Makefile:239: recipe for target 'release' failed
make: *** [release] Error 1
"><pre class="notranslate"><code class="notranslate">+++ [0930 02:04:05] Starting etcd instance
etcd --advertise-client-urls http://127.0.0.1:2379 --data-dir /tmp.k8s/tmp.fcfyJnEiqq --listen-client-urls http://127.0.0.1:2379 --debug &gt; "/dev/null" 2&gt;/dev/null
Waiting for etcd to come up.
+++ [0930 02:04:05] On try 1, etcd: :
{"action":"set","node":{"key":"/_test","value":"","modifiedIndex":3,"createdIndex":3}}
+++ [0930 02:04:06] Running integration test cases
Running tests for APIVersion: v1,apps/v1alpha1,authentication.k8s.io/v1beta1,authorization.k8s.io/v1beta1,autoscaling/v1,batch/v1,batch/v2alpha1,certificates.k8s.io/v1alpha1,
extensions/v1beta1,imagepolicy.k8s.io/v1alpha1,policy/v1alpha1,rbac.authorization.k8s.io/v1alpha1,storage.k8s.io/v1beta1
+++ [0930 02:04:07] Running tests without code coverage
# k8s.io/kubernetes/test/e2e/framework
test/e2e/framework/gobindata_util.go:30: undefined: generated.Asset
test/e2e/framework/gobindata_util.go:33: undefined: generated.AssetNames
Makefile:118: recipe for target 'test' failed
make[1]: *** [test] Error 1
+++ [0930 02:05:19] Cleaning up etcd
+++ [0930 02:05:19] Integration test cleanup complete
Makefile:130: recipe for target 'test-integration' failed
make: *** [test-integration] Error 1
Makefile:239: recipe for target 'release' failed
make: *** [release] Error 1

</code></pre></div>
<p dir="auto"><strong>What you expected to happen</strong>:</p>
<p dir="auto">Build to complete</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<p dir="auto">git pull; make release</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>
<p dir="auto">I saw the same thing yesterday on a slightly older commit, so this is not a very recent regression.</p>
<p dir="auto">Something like:</p>
<div class="highlight highlight-source-yaml notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="rules:
- host: foo.bar.com
  path: /api
  backend:
  - serviceName: alpha1
    weight: 1, or 33%
  - serviceName: alpha2
    weight: 2, or 66%"><pre class="notranslate"><span class="pl-ent">rules</span>:
- <span class="pl-ent">host</span>: <span class="pl-s">foo.bar.com</span>
  <span class="pl-ent">path</span>: <span class="pl-s">/api</span>
  <span class="pl-ent">backend</span>:
  - <span class="pl-ent">serviceName</span>: <span class="pl-s">alpha1</span>
    <span class="pl-ent">weight</span>: <span class="pl-s">1, or 33%</span>
  - <span class="pl-ent">serviceName</span>: <span class="pl-s">alpha2</span>
    <span class="pl-ent">weight</span>: <span class="pl-s">2, or 66%</span></pre></div>
<p dir="auto">There'er ways to achieve similar splitting with either a deployment or by managing Service labels so they span a mix of alpha1 and alpha2 endpoints, but this seems more intuitive.</p>
<p dir="auto">On GCE I think we'd have to use iptables stats to  satisfy that, but we can't push it down into a Service because today a single Service only understands homogenous endpoints.</p>
<p dir="auto">Nginx and haproxy understand wrr, so the 33% and 66% would have to apply to all the endpoints of the Service, and we'd just need to make sure the tie is broken evenly.</p>