<p>I'm looking for a way to find:</p>
<ol>
<li>The current usage of CPU and RAM of each pod running.</li>
<li>The configured CPU and RAM of each pod.</li>
</ol>
<p>One side is to identify the resource usage, and the other is to identify if it was patched manually or via the deploy YAML.</p>

Frank N Stein
<p>You can deploy a <a href="https://github.com/kubernetes-sigs/metrics-server" rel="nofollow noreferrer">metrics-server</a> on your cluster to get resources usage:</p>
<blockquote>
<p>Metrics Server is a scalable, efficient source of container resource
metrics for Kubernetes built-in autoscaling pipelines [...] Metrics API can also be accessed by <code>kubectl top</code> [...]</p>
</blockquote>
<p>Then you can use <code>kubectl top</code> to view current resources usage. e.g.:</p>
<pre><code>$ kubectl top pods --all-namespaces
NAMESPACE     NAME                                        CPU(cores)   MEMORY(bytes)   
kube-system   coredns-74ff55c5b-vgfzw                     5m           13Mi            
kube-system   etcd-minikube                               32m          46Mi            
kube-system   ingress-nginx-controller-65cf89dc4f-crrr9   6m           204Mi           
kube-system   kube-apiserver-minikube                     99m          295Mi           
kube-system   kube-controller-manager-minikube            32m          53Mi            
kube-system   kube-proxy-9mfb9                            0m           23Mi            
kube-system   kube-scheduler-minikube                     4m           17Mi            
kube-system   metrics-server-56c4f8c9d6-48rdd             1m           12Mi            
kube-system   storage-provisioner                         2m           9Mi
</code></pre>
<hr />
<p>You can <code>kubectl describe nodes</code> to get an overview of requests/limits configurations for pods running on each node. e.g.:</p>
<pre><code>Non-terminated Pods:          (13 in total)
  Namespace                   Name                                         CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                   ----                                         ------------  ----------  ---------------  -------------  ---
  default                     my-nginx-5b56ccd65f-txkfg                    0 (0%)        0 (0%)      0 (0%)           0 (0%)         4m48s
  default                     my-nginx-5b56ccd65f-wkhms                    0 (0%)        0 (0%)      0 (0%)           0 (0%)         4m48s
  kube-system                 coredns-74ff55c5b-vgfzw                      100m (0%)     0 (0%)      70Mi (0%)        170Mi (1%)     4d
  kube-system                 etcd-minikube                                100m (0%)     0 (0%)      100Mi (0%)       0 (0%)         17h
  kube-system                 ingress-nginx-controller-65cf89dc4f-crrr9    100m (0%)     0 (0%)      90Mi (0%)        0 (0%)         3d23h
  kube-system                 kube-apiserver-minikube                      250m (2%)     0 (0%)      0 (0%)           0 (0%)         17h
  kube-system                 kube-controller-manager-minikube             200m (1%)     0 (0%)      0 (0%)           0 (0%)         4d
  kube-system                 kube-proxy-9mfb9                             0 (0%)        0 (0%)      0 (0%)           0 (0%)         4d
  kube-system                 kube-scheduler-minikube                      100m (0%)     0 (0%)      0 (0%)           0 (0%)         4d
  kube-system                 metrics-server-56c4f8c9d6-48rdd              0 (0%)        0 (0%)      0 (0%)           0 (0%)         4m18s
  kube-system                 my-nginx-5b56ccd65f-96n7v                    0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d23h
  kube-system                 my-nginx-5b56ccd65f-sm7w5                    0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d23h
  kube-system                 storage-provisioner                          0 (0%)        0 (0%)      0 (0%)           0 (0%)         4d
</code></pre>
<p><code>0</code> means no request/limits defined.</p>
