anchor.diff:  
   . Check the real-time kernel: Once each impacted node reboots, log in to the cluster
   and run the following commands to make sure that the real-time kernel has
  -replaced the regular kernel for the set of worker or master nodes you
  +replaced the regular kernel for the set of nodes you
   configured:
   +
   [source,terminal]
  
positive.code: 
  . Create a MachineConfig for the real-time kernel: Create a YAML file
  (for example, `99-worker-realtime.yaml`) that contains a MachineConfig
  object  for the `realtime` kernelType. This example tells the cluster to
  use a real-time kernel for all worker nodes:
  +
  [source,terminal]
  
negative.code: system with real-time characteristics.
  
  If your {product-title} workloads require these real-time characteristics,
  you can switch your machines to the Linux
  real-time kernel. For {product-title}, {product-version} you can make this
  switch using a MachineConfig object. Although making the change is as simple
  as changing a MachineConfig `kernelType` setting to `realtime`, there are a few
  other considerations before making the change:
  
  * Currently, real-time kernel is supported only on worker nodes, and only for radio access network (RAN) use.
  * The following procedure is fully supported with bare metal installations that use
  systems that are certified for Red Hat Enterprise Linux for Real Time 8.
  * Real-time support in {product-title} is limited to specific subscriptions.
  * The following procedure is also supported for use with Google Cloud Platform.
  
  .Prerequisites
  * Have a running {product-title} cluster (version 4.4 or later).
  