Implement "Caching Scan Results by Image Reference"

[neiser]

I'm interested in the status of the document Caching Scan Results by Image Reference, as my team would really appreciate such a feature being implemented. The document reads as if there was already some implementation attempt for the operator code here, but I can't find any pull request or reference in the document to that code. I also checked in the original starboard repo and only found a similar document.

Telling from the git history, maybe @NissesSenap or @danielpacak can comment how far implementation-wise this feature is? Also, maybe @chen-keinan knows? I hope it's ok that I mention you guys directly.

Any pointer is appreciated, and if you don't have any objections, I could try and start implementation of this feature on my own.

[NissesSenap]

@neiser I started looking in to it in the starboard project but I haven't been active in the aquasecurity project in a long time so I can't remember to be honest.

I know that @danielpacak started on a PR before he stopped and instead wrote a design document that I gave some feedback on: aquasecurity/starboard#740.

But I don't think anything was done after that but as I said I haven't been active in trivy-operator project.
Here @chen-keinan could give some insight.

I would love to see the feature and If you have time to look at it I think go for it :).

[neiser]

@NissesSenap Thanks for that super quick reply!

[chen-keinan]

@neiser this could be a very good feature and go for it 🚀 few points :

• TTL - today each report has by default TTL (24h , configurable) , I think will be good to keep it for vulnerability cluster reports (avoid false negative)
• GC - not sure if it is a must as we have TTL but today each report own by one resource
• it will be great to make it configurable

[neiser]

I've updated the issue title to reflect that we should/can implement this feature.

[github-actions]

This issue is stale because it has been labeled with inactivity.

[github-actions]

This issue is stale because it has been labeled with inactivity.

[sathieu]

not stale.

@chen-keinan Please add the relevant label to prevent this issue to be marked as stale in the future 🙏.

[github-actions]

This issue is stale because it has been labeled with inactivity.

[sathieu]

still not stale.

[github-actions]

This issue is stale because it has been labeled with inactivity.

[github-actions]

This issue is stale because it has been labeled with inactivity.

[sathieu]

This would still be useful.