anchor.diff:  * The number of producers and consumers
   * The number of topics and partitions
   
  -The values specified for resource requests are reserved and always available to a container.
  +The values specified for resource requests are reserved and always available to the container.
   Resource limits specify the maximum resources that can be consumed by a given container.
   The amount between the request and limit is not reserved and might not be always available.
   A container can use the resources up to the limit only when they are available.
  
positive.code: If `-Xms` is set to `-Xmx`, the container will crash immediately; if not, the container will crash at a later time.
  
  In this example, the JVM uses 2 GiB (=2,147,483,648 bytes) for its heap.
  Its total memory usage is approximately 8GiB.
  
  .Example `-Xmx` and `-Xms` configuration
  [source,yaml,subs=attributes+]
  
negative.code: 
  .`-Xms` and `-Xmx` options
  
  In addition to setting memory request and limit values for your containers, you can use the `-Xms` and `-Xmx` JVM options to set specific heap sizes for your JVM.
  Use the `-Xms` option to set an initial heap size and the `-Xmx` option to set a maximum heap size.
  
  Specify heap size to have more control over the memory allocated to your JVM.
  Heap sizes should make the best use of a container's xref:con-common-configuration-resources-reference[memory limit (and request)] without exceeding it.
  Heap size and any other memory requirements need to fit within a specified memory limit.
  If you don't specify heap size in your configuration, but you configure a memory resource limit (and request), the Cluster Operator imposes default heap sizes automatically.
  The Cluster Operator sets default maximum and minimum heap values based on a percentage of the memory resource configuration.
  
  The following table shows the default heap values.
  
  