Image Scanner -> Policy Report Adapter

[JimBugwadia]

Develop an adapter to execute a periodic or event based image scan and convert results and to generate or update a Policy Report custom resource based on the WG Policy CRD.

The tasks involved are:

1. Research available OSS image scanners like Clair and Trivy
2. Design how the scan should be run i.e. when a new image pull happens or periodically
3. Run the scan as a CronJob and produce the Policy Report CRD

[adeniyistephen]

Hi, I'm Stephen, I saw this project on the LFX projects and it needs a mentee for the project. I would love to work on this Image Scanner and also the Falco project, I was once a small Kubernetes contributor and terraform, I have not worked with Falco before or built a Policy report before, but I have worked with Go adapter on two different projects.

[JimBugwadia]

Hi @adeniyistephen - thanks for your interest and welcome to the working group! Please feel free to ask questions here or on our slack channel (https://kubernetes.slack.com/archives/C906A4GAF) to help you draft a proposal.

[adeniyistephen]

@JimBugwadia Can't wait to 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

[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

[JimBugwadia]

Closed via #88.