anchor.diff:  +
   [source,terminal]
   ----
  -$ base64 -w0 <installation_directory>/bootstrap.ign > <installation_directory>/bootstrap.64
  +$ base64 -w0 <installation_directory>/merge-bootstrap.ign > <installation_directory>/merge-bootstrap.64
   ----
   +
   [IMPORTANT]
  
positive.code: +
  *** Optional: In the event of cluster performance issues, from the *Latency Sensitivity* list, select *High*.
  *** Click *Edit Configuration*, and on the *Configuration Parameters* window, click *Add Configuration Params*. Define the following parameter names and values:
  **** `guestinfo.ignition.config.data`: Paste the contents of the base64-encoded Ignition config file for this machine type. Note for the bootstrap node, the Ignition config file must be provided in `guestinfo.ignition.config.data` in the *Configuration Parameters* window. This is due to a restriction in the maximum size of data that can be provided in a vApp property.
  **** `guestinfo.ignition.config.data.encoding`: Specify `base64`.
  **** `disk.EnableUUID`: Specify `TRUE`.
  *** Alternatively, prior to powering on the virtual machine, use vApp properties to:
  **** Navigate to a virtual machine from the vCenter Server inventory.
  **** On the *Configure* tab, expand *Settings* and select *vApp options.*
  **** Scroll down and under *Properties*, apply the configurations that you just edited.
  .. In the *Virtual Hardware* panel of the *Customize hardware* tab, modify the specified values as required. Ensure that the amount of RAM, CPU, and disk storage meets the minimum requirements for the
  machine type.
  .. Complete the configuration and power on the VM.
  
negative.code: 
  .Prerequisites
  
  * You have obtained the Ignition config files for your cluster.
  * You have access to an HTTP server that you can access from your computer and that the machines that you create can access.
  * You have created a link:https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.vcenterhost.doc/GUID-B1018F28-3F14-4DFE-9B4B-F48BBDB72C10.html[vSphere cluster].
  
  .Procedure
  
  . Upload the bootstrap Ignition config file, which is named `<installation_directory>/bootstrap.ign`, that the installation program created to your HTTP server. Note the URL of this file.
  +
  . Save the following secondary Ignition config file for your bootstrap node to your computer as `<installation_directory>/merge-bootstrap.ign`:
  +
  [source,text]
  ----
  {
    "ignition": {
      "config": {
        "merge": [
          {
            "source": "<bootstrap_ignition_config_url>", <1>
            "verification": {}
          }
        ]
      },
      "timeouts": {},
      "version": "3.2.0"
    },
    "networkd": {},
    "passwd": {},
    "storage": {},
    "systemd": {}
  }
  ----
  +
  <1> Specify the URL of the bootstrap Ignition config file that you hosted.
  +
  When you create the virtual machine (VM) for the bootstrap machine, you use this Ignition config file.
  +
  . Locate the following Ignition config files that the installation program created:
  +
  * `<installation_directory>/master.ign`
  * `<installation_directory>/worker.ign`
  * `<installation_directory>/merge-bootstrap.ign`
  +
  . Convert the Ignition config files to Base64 encoding. Later in this procedure, you must add these files to the extra configuration parameter `guestinfo.ignition.config.data` in your VM.
  +
  For example, if you use a Linux operating system, you can use the `base64` command to encode the files.
  +
  