Description of problem:

    File integrity operator fails with compliance operator functionality
When compliance operator is installed and runs its first scan /etc/kubernetes/compliance-operator file integrity operator fails

Only way to avoid this is excluding the /etc/kubernetes otherwise reinitializing the AIDE database after the alert.

In this way the FIO operator does not work with other redhat provided operators too 

The Customer also said, 
"we can't exclude /etc/kubernetes/compliance-operator because the file-integrity-operator will still alert for changed link count in /etc/kubernetes. Excluding /etc/kubernetes doesn't really make sense .Actually the file-integrity-operator in it's current state is completely broken and useless. It does not work together with other operators provided by RedHat, not even with base functionality of ovn provided with OpenShift itself. We will uninstall the file-integrity-operator".

Referred the Following document for file integrity operator.

• https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/security_and_compliance/file-integrity-operator#file-integrity-operator-advanced-usage