anchor.diff:  +
   [NOTE]
   ====
  -The `99-worker-console.bu` file is set to create a machine config for worker nodes. To deploy on control plane nodes, change the role from `worker` to `master`. To do both, you could repeat the whole procedure using different file names for the two types of deployments.
  +The `99-worker-custom.bu` file is set to create a machine config for worker nodes. To deploy on control plane nodes, change the role from `worker` to `master`. To do both, you could repeat the whole procedure using different file names for the two types of deployments.
   ====
   
   . Create a `MachineConfig` object by giving Butane the file that you created in the previous step:
   +
   [source,terminal]
   ----
  -$ butane 99-worker-console.bu -o ./99-worker-console.yaml
  +$ butane 99-worker-custom.bu -o ./99-worker-custom.yaml
   ----
   +
   A `MachineConfig` object YAML file is created for you to finish configuring your machines.
  
positive.code: 
  .Procedure
  
  . Create a Butane config file. The following example creates a file named `99-worker-console.bu` that configures the system console to use the second serial port and specifies custom settings for the chrony time service:
  +
  [source,yaml]
  ----
  variant: openshift
  version: 4.8.0
  metadata:
    name: 99-worker-console
    labels:
      machineconfiguration.openshift.io/role: worker
  openshift:
    kernel_arguments:
      - console=ttyS1,115200
  storage:
    files:
      - path: /etc/chrony.conf
  
negative.code: +
  [source,terminal]
  ----
  $ oc create -f 99-worker-custom.yaml
  ----
  