modifies the detect enforcer function in the controller

[swastik959]

Purpose of PR?: kubearmor makes use of /sys/kernel/security/lsm to detect enforcer this can be removed as the operator now deploys the snitch which detects the enforcer and adds it to the node label Fixes #1389

Does this PR introduce a breaking change?

If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? : Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

• [ ] Bug fix. Fixes #
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update
• [ ] PR Title follows the convention of <type>(<scope>): <subject>
• [ ] Commit has unit tests
• [ ] Commit has integration tests

[rksharma95]

@swastik959 thanks for your contribution, can you also handle the deployment related changes with this PR itself.

[Ankurk99]

if someone deploys the kubearmor using the karmor cli then these labels are present.

using the karmor cli then these labels are not present. Correct :+1:

[swastik959]

@nyrahul can you create a seperate issue for that I would like to work on it .

[DelusionalOptimist]

Folks, FYI kubearmor-client now installs KubeArmor using the operator, since it was a blocker to this PR earlier. cc @swastik959 @rksharma95 @kranurag7

[Aryan-sharma11]

Resolved with #1335. Thanks for the PR @swastik959