<p>We are running Kubernetes with the following configuration:
On-premise Kubernetes 1.11.3, cri-o 1.11.6 and CentOS7 with UEK-4.14.35</p>

<p>I can't make <em>crictl stats</em> to return pods information, it returns empty list only. Has anyone run into the same problem?</p>

<p>Another issue we have, is that when I query the kubelet for stats/summary it returns an empty pods list.</p>

<p>I think that these two issues are related, although I am not sure which one of them is the problem.</p>

alubin
<p>I would recommend checking <code>kubelet</code> service to verify health status and debug any suspicious events within the cluster. I assume that <a href="https://github.com/kubernetes-sigs/cri-o" rel="nofollow noreferrer">CRI-O</a> runtime engine can select <code>kubelet</code> as the main Pods information provider because of its managing Pod lifecycle role.</p>

<pre><code>systemctl status kubelet -l

journalctl -u kubelet
</code></pre>

<p>In case you found some errors or dubious events, share it in a comment below this answer.</p>

<p>However, you can use <a href="https://github.com/kubernetes-incubator/metrics-server" rel="nofollow noreferrer">metrics-server</a>, which will collect Pod metrics in the cluster and enable <code>kube-apiserver</code> flags for <a href="https://kubernetes.io/docs/tasks/access-kubernetes-api/configure-aggregation-layer/" rel="nofollow noreferrer">Aggregation Layer</a>. Here is a good <a href="https://docs.bitnami.com/kubernetes/how-to/configure-autoscaling-custom-metrics/" rel="nofollow noreferrer">article</a> about Horizontal Pod Autoscaling and monitoring resources via <a href="https://github.com/prometheus/prometheus" rel="nofollow noreferrer">Prometheus</a>.</p>
