anchor.diff:  IMPORTANT: Containers doing lots of disk I/O (such as Kafka broker containers) will need to leave some memory available for use as operating system page cache.
   On such containers, the requested memory should be significantly higher than the memory used by the JVM.
   
  -.Example fragment configuring `-Xmx`
  +.Example fragment configuring `-Xmx` and `-Xms`
   [source,yaml,subs=attributes+]
   ----
   # ...
  
positive.code: Only a selected subset of available JVM options can be configured.
  The following options are supported:
  
  .-Xms
  
  `-Xms` configures the minimum initial allocation heap size when the JVM starts.
  
  .-Xmx
  
  `-Xmx` configures the maximum heap size.
  
  NOTE: The units accepted by JVM settings such as `-Xmx` and `-Xms` are those accepted by the JDK `java` binary in the corresponding image.
  
negative.code: In the above example, the JVM will use 2 GiB (=2,147,483,648 bytes) for its heap.
  Its total memory usage will be approximately 8GiB.
  
  Setting the same value for initial (`-Xms`) and maximum (`-Xmx`) heap sizes avoids the JVM having to allocate memory after startup, at the cost of possibly allocating more heap than is really needed.
  For Kafka and Zookeeper pods such allocation could cause unwanted latency.
  For Kafka Connect avoiding over allocation may be the most important concern, especially in distributed mode where the effects of over-allocation will be multiplied by the number of consumers.
  
  .-server
  
  