anchor.diff:  	- CPU: 150m
   	- Memory: 100Mi
   
  -The cluster can schedule 52 instance(s) of the pod small-pod.
  +The cluster can schedule 88 instance(s) of the pod small-pod.
   
  -Termination reason: Unschedulable: No nodes are available that match all of the
  -following predicates:: Insufficient cpu (2).
  +Termination reason: Unschedulable: 0/5 nodes are available: 2 Insufficient cpu,
  +3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't
  +tolerate.
   
   Pod distribution among nodes:
   small-pod
  -	- 192.168.124.214: 26 instance(s)
  -	- 192.168.124.120: 26 instance(s)
  +	- 192.168.124.214: 45 instance(s)
  +	- 192.168.124.120: 43 instance(s)
   ----
   +
   In the above example, the number of estimated pods that can be scheduled onto
  -the cluster is 52.
  +the cluster is 88.
  
positive.code: 
  .Prerequisites
  
  * Download and install link:https://github.com/kubernetes-incubator/cluster-capacity[the *cluster-capacity* tool].
  
  * Create a sample `Pod` spec file, which the tool uses for estimating resource usage. The `podspec` specifies its resource
  requirements as `limits` or `requests`. The cluster capacity tool takes the
  
negative.code: 
  .Procedure
  
  To use the cluster capacity tool on the command line:
  
  . From the terminal, log in to the Red Hat Registry:
  +
  [source,terminal]
  ----
  $ podman login registry.redhat.io
  ----
  
  . Pull the cluster capacity tool image:
  +
  [source,terminal]
  ----
  $ podman pull registry.redhat.io/openshift4/ose-cluster-capacity
  ----
  
  . Run the cluster capacity tool:
  +
  [source,terminal]
  ----
  $ podman run -v $HOME/.kube:/kube:Z -v $(pwd):/cc:Z  ose-cluster-capacity \
  /bin/cluster-capacity --kubeconfig /kube/config --podspec /cc/pod-spec.yaml \
  --verbose <1>
  ----
  <1> You can also add the `--verbose` option to output a detailed description of how many pods can be scheduled on each node in the cluster.
  +
  .Example output
  [source,terminal]
  