Trivy or Trivy Operator?

[raisalsalim]

I’m looking to set up container image scanning in my Kubernetes cluster and am trying to decide between using Trivy and Trivy Operator. Could someone clarify the differences between them?

From what I understand, Trivy is a standalone scanner, while Trivy Operator provides continuous scanning capabilities within the cluster. I’d like to confirm if Trivy Operator is the recommended choice for continuous or scheduled scanning directly in Kubernetes, or if I could achieve similar functionality with standalone Trivy.

My specific use case is to schedule scans once a week for all container images in my Kubernetes cluster. Any advice on which option would be better suited for this, and whether additional configuration is needed to set up weekly scans?