Red Hat High Availability and Resilient Storage should support kpatch in running clusters.

This is a test only issue as there should be no development effort needed (and I expect the kernel patches to be installed without any impact to the cluster or GFS2).

To test we should take a running cluster (2 nodes and 3 nodes) under load and apply a kernel patch for the specified running kernel with the following commands:

(Optional - see what kernel patches are available)

1. yum search $(uname -r)
   (Install the patch)
2. yum install "kpatch-patch = $(uname -r)"
    
   If the only kpatch-patch version ends in "0-0" it is an empty patch and should not be used.
   You can run "kpatch list" before and after the 'yum install' command to verify there are no kernel patches installed at the start and that there is one installed after it has completed.
   Each node in the cluster should have the kpatch installed in sequence, so we only have one node being upgraded at a time.

More documentation about kpatch is here - https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/applying-patches-with-kernel-live-patching_managing-monitoring-and-updating-the-kernel#applying-patches-with-kernel-live-patching_managing-monitoring-and-updating-the-kernel