KubeArmor support for producing PolicyReport CRs

[rficcaglia]

Currently KubeArmor produces bespoke Log output.

This feature request will add support for producing a Policy Report from KubeArmor. The implementation could be a native contribution to KubeArmor or an adapter that runs alongside KubeArmor and creates / updates the policy report.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[JimBugwadia]

@nyrahul - is this something best done natively in KubeArmor or as an adapter?

[nyrahul]

@nyrahul - is this something best done natively in KubeArmor or as an adapter?

I believe this is best handled as an adapter since there are few users of kubearmor who might not want the policy report logs to be changed.

[rficcaglia]

maybe that is an opportunity for user community education? ie if we can show the benefits of using a common report format vs. custom 1-off outputs that need to be normalized for cross-component reporting there would be less (or no) pushback

…

On Mon, Aug 9, 2021 at 6:26 AM Rahul Jadhav ***@***.***> wrote: @nyrahul </~https://github.com/nyrahul> - is this something best done natively in KubeArmor or as an adapter? I believe this is best handled as an adapter since there are few users of kubearmor who might not want the policy report logs to be changed. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#59 (comment)>, or unsubscribe </~https://github.com/notifications/unsubscribe-auth/AAGENIV2H3BJNUFSWMFRAALT37JPNANCNFSM44OJXNCQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[jimil749]

Hello @JimBugwadia! Came across this via the CNCF mentorship repo. Would love to get involved. Any pointers to get started? 😅

[JimBugwadia]

@jimil749 - thanks for your interest in contributing! You can take a look at the policy report CRD definition and KubeArmor's current output format as a start.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[JimBugwadia]

/remove-lifecycle stale