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: 
  .Procedure
  
  To use the tool on the command line: 
  
  . Run the following command:
  +
  [source,terminal]
  ----
  $ ./cluster-capacity --kubeconfig <path-to-kubeconfig> \ <1>
      --podspec <path-to-pod-spec> <2>
  ----
  <1> Specify the path to your Kubernetes configuration file.
  <2> Specify the path to the sample `Pod` spec file
  +
  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:
  +
  [source,terminal]
  ----
  $ ./cluster-capacity --kubeconfig <path-to-kubeconfig> \
      --podspec <path-to-pod-spec> --verbose
  ----
  +
  .Example output
  [source,terminal]
  
negative.code: 
  .Prerequisites
  
  * Run the link:https://catalog.redhat.com/software/containers/openshift4/ose-cluster-capacity/5cca0324d70cc57c44ae8eb6?container-tabs=overview[OpenShift Cluster Capacity Tool], which is available as a container image from the Red Hat Ecosystem Catalog.
  
  * 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
  