anchor.diff:  $ git clone https://github.com/kmods-via-containers/kvc-simple-kmod
   ----
   
  -. Get your module software. In this example, `kvc-simple-kmod` is used:
  +. Get your module software. In this example, `kvc-simple-kmod` is used.
   
   . Create a fakeroot directory and populate it with files that you want to
   deliver via Ignition, using the repositories cloned earlier:
  
positive.code: # yum install podman make git -y
  ----
  
  . Create an Ignition config file that creates a systemd unit file:
  .. Create a directory to host the Ignition config file:
  +
  [source,terminal]
  ----
  $ mkdir kmods; cd kmods
  ----
  
  .. Create the Ignition config file that creates a systemd unit file:
  +
  [source,terminal]
  ----
  $ cat <<EOF > ./baseconfig.ign
  {
    "ignition": { "version": "3.2.0" },
    "passwd": {
      "users": [
        {
          "name": "core",
          "groups": ["sudo"],
          "sshAuthorizedKeys": [
            "ssh-rsa AAAA"
          ]
        }
      ]
    },
    "systemd": {
      "units": [{
        "name": "require-kvc-simple-kmod.service",
        "enabled": true,
        "contents": "[Unit]\nRequires=kmods-via-containers@simple-kmod.service\n[Service]\nType=oneshot\nExecStart=/usr/bin/true\n\n[Install]\nWantedBy=multi-user.target"
      }]
    }
  }
  EOF
  ----
  +
  [NOTE]
  ====
  You must add your public SSH key to the `baseconfig.ign` file
  to use the file during `openshift-install`.
  The public SSH key is not needed if you create the `MachineConfig` object using the MCO.
  ====
  
  . Create a base MCO YAML snippet that uses the following configuration:
  +
  [source,terminal]
  ----
  $ cat <<EOF > mc-base.yaml
  apiVersion: machineconfiguration.openshift.io/v1
  kind: MachineConfig
  metadata:
    labels:
      machineconfiguration.openshift.io/role: worker
    name: 10-kvc-simple-kmod
  spec:
    config:
  EOF
  ----
  +
  [NOTE]
  ====
  The `mc-base.yaml` is set to deploy the kernel module on `worker` nodes.
  To deploy on master 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.
  ====
  
  . Get the `kmods-via-containers` software:
  
  .. Clone the `kmods-via-containers` repository:
  
negative.code: deliver that software to worker or master nodes at installation time
  or via the Machine Config Operator.
  
  .Procedure
  
  . Register a RHEL 8 system:
  +
  