feat: added kubectl exec alert policy

[yp969803]

Signed-off-by: Yash Patel [email protected]

Purpose of PR?: added kubectl exec alert policy

Fixes #1750

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

[yp969803]

@daemon1024 can you review the current work

[yp969803]

@daemon1024 cab u run the tests

[daemon1024]

Hey @yp969803
Appreciate the attempt at the problem statement. The scope of the problem is very different. It involves construction of entirely new spec for KubeArmor Policy. I will try to update #1750 with more details, but this is definitely not in the same direction of solution what the problem statement demands to be.

[yp969803]

@daemon1024 sorry for misunderstanding the issue, i thought you wanted a defualt policy for all the pods which audit kubectl exec.