KubeArmor daemonset pods failing to deploy successfully, preventing cluster storage from provisioning

[mikemcd3912]

Describe the bug
The Kubearmor controller and relay pods start up and enter a 'ready' state, but the daemonset pods for all nodes enter a CrashLoopBackOff state shortly after deployment . The logs for the daemonset Kuberarmor container in the daemonset pods show that shortly after start the container begins to drop events due to replay timeouts. The failing deployment also causes the openebs PVC provisioner to fail to create new claims, preventing other workloads on the cluster from obtaining storage necessary to their successful function and deployment

To Reproduce
Deploy KubeArmor on EKS anywhere Baremetal

Expected behavior
Daemonset to successfully deploy and operate

Screenshots

kubearmor logs.txt

Desktop (please complete the following information):

• EKS Anywhere Baremetal environment
• Kubernetes Version 1.27
• Ubuntu 20.04.6 LTS Nodes

Additional context
Add any other context about the problem here.

[mikemcd3912]

Closed by PR #235