anchor.diff:  .Cluster CPU overhead
   
   ----
  -CPU overhead for infrastructure nodes ≈ 4
  +CPU overhead for infrastructure nodes ≈ 4 cores
   ----
   
  +{VirtProductName} increases the overall utilization of cluster level services such as logging, routing, and monitoring. To account for this workload, ensure that nodes that host infrastructure components have capacity allocated for 4 additional cores (4000 millicores) distributed across those nodes.
  +
   ----
  -CPU overhead for worker nodes ≈ 2 + CPU overhead per virtual machine
  +CPU overhead for worker nodes ≈ 2 cores + CPU overhead per virtual machine
   ----
  +
  +Each worker node that hosts virtual machines must have capacity for 2 additional cores (2000 millicores) for {VirtProductName} management workloads in addition to the CPUs required for virtual machine workloads.
  +
   
   .Virtual machine CPU overhead
   
  -CPU overhead per virtual machine is subjective. If dedicated CPUs are requested, there is a 1:1 impact on the cluster CPU overhead requirement. Otherwise, there are no specific rules about how many CPUs a virtual machine requires.
  +If dedicated CPUs are requested, there is a 1:1 impact on the cluster CPU overhead requirement. Otherwise, there are no specific rules about how many CPUs a virtual machine requires.
   
   
   [id="storage-overhead_{context}"]
  
positive.code: 
  ----
  Memory overhead per virtual machine ≈ (1.002 * requested memory) + 146 MiB  \
                  + (8 * number of vCPUs) + (16 MiB * number of graphics devices)
  ----
  
  Add 1 GiB to the above result if your environment includes a Single Root I/O Virtualization (SR-IOV) network device or a Graphics Processing Unit (GPU).
  
  
  [id="CPU-overhead_{context}"]
  
negative.code: [id="example-scenario_{context}"]
  == Example
  
  As a cluster administrator, if you plan to host 10 virtual machines in the cluster, each with 1 GiB of RAM and 2 vCPUs, the memory impact across the cluster is 11.68 GiB. The estimated on-disk storage impact for each node in the cluster is 10 GiB and the CPU impact for worker nodes that host virtual machine workloads is a minimum of 2 cores.
  