anchor.diff:  `coreos-installer` that let you retain existing data partitions.
   
   [id="installation-user-infra-machines-advanced_vardisk_{context}"]
  -=== Creating a separate /var partition
  +=== Creating a separate `/var` partition
   In general, disk partitioning for {product-title} should be left to the
   installer. However, there are cases where you might want to create a
   separate partition in a part of the filesystem that you expect to grow.
  
positive.code: * Creating separate partitions: For greenfield installations on an empty
  disk, you may want to add separate storage to a partition. This is only
  officially supported for making `/var` or a subdirectory of `/var` a separate
  partition (not both). If you create more than one partitoin, Kubernetes
  will not be able to monitor them both.
  
  * Retaining existing partitions: For a brownfield installation, where you
  
negative.code: 
  * `/var/lib/containers`: Holds container-related content that can grow
  as more images and containers are added to a system.
  * `/var`: Holds data that you might want to keep separate for purposes such as
  auditing.
  
  Storing the contents of a `/var` directory separately allows you to more easily
  grow storage to those areas as needed, and to reinstall {product-title}
  at a later date and keep that data intact. In other words, you would not have
  to pull all your containers again or copy off massive log files when you
  update your systems.
  