<p dir="auto">Would be nice to have <code class="notranslate">kubectl stats podName</code> work like docker stats (basically a top like interface on the client that connects to an endpoint streaming data every second).  I think this should be pretty straightforward, since the kubelet server already supports requests for <code class="notranslate">/stats/ns/podname/uid/containername</code></p>
<p dir="auto">Would be even better to have kubectl show stats consumed by a service, rc across the cluster.</p>
<p dir="auto">We saw this in Jenkins. The following loops until the test is killed:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[1] INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
[1] INFO: POD                           NODE                    PHASE   CONDITIONS
[1] INFO: kube-ui-v1-bp9s2              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-dk10d              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-eahns              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-zvxka              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: monitoring-heapster-v5-5v5rp  pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: 
[1] INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
[1] INFO: POD                           NODE                    PHASE   CONDITIONS
[1] INFO: kube-ui-v1-bp9s2              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-dk10d              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-eahns              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-zvxka              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: monitoring-heapster-v5-5v5rp  pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: 
[1] INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
[1] INFO: POD                           NODE                    PHASE   CONDITIONS
[1] INFO: kube-ui-v1-bp9s2              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-dk10d              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-eahns              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-zvxka              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: monitoring-heapster-v5-5v5rp  pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: 
..."><pre class="notranslate"><code class="notranslate">[1] INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
[1] INFO: POD                           NODE                    PHASE   CONDITIONS
[1] INFO: kube-ui-v1-bp9s2              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-dk10d              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-eahns              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-zvxka              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: monitoring-heapster-v5-5v5rp  pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: 
[1] INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
[1] INFO: POD                           NODE                    PHASE   CONDITIONS
[1] INFO: kube-ui-v1-bp9s2              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-dk10d              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-eahns              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-zvxka              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: monitoring-heapster-v5-5v5rp  pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: 
[1] INFO: 9 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
[1] INFO: POD                           NODE                    PHASE   CONDITIONS
[1] INFO: kube-ui-v1-bp9s2              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-dk10d              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-eahns              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: kube-ui-v1-zvxka              pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: monitoring-heapster-v5-5v5rp  pull-e2e-2-minion-yl9w  Failed  []
[1] INFO: 
...
</code></pre></div>
<p dir="auto">I saw this once so haven't yet assessed its frequency.</p>
<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/ixdy/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ixdy">@ixdy</a> says he thinks he has seen the same failure a few times, and linked artifacts (for those with permissions):<br>
<a href="https://console.developers.google.com/storage/browser/kubernetes-jenkins/pr-logs/739cb2f526f15e7c82ef7c476a1458ad68b09fd1/kubernetes-pull-build-test-e2e-gce/2246/_artifacts/" rel="nofollow">https://console.developers.google.com/storage/browser/kubernetes-jenkins/pr-logs/739cb2f526f15e7c82ef7c476a1458ad68b09fd1/kubernetes-pull-build-test-e2e-gce/2246/_artifacts/</a></p>
<p dir="auto">+cc <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/rjnagal/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/rjnagal">@rjnagal</a> for labeling/triage/xref:<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="94161337" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/11018" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes/kubernetes/pull/11018/hovercard" href="https://github.com/kubernetes/kubernetes/pull/11018">#11018</a></p>