Component: Scanner V4 / Scanner V4 DB
RHACS/StackRox version: 4.10.2
Deployment method: Helm chart (stackrox-central-services)

Description:
The scanner-v4-db PVC is consuming significantly more disk space than expected. Disk usage reached ~16GB within a few weeks of normal operation. The PVC was explicitly sized (not left at default), and usage is approaching/has reached that limit.
Steps to reproduce / observed behavior:
Deploy stackrox-central-services via Helm with Scanner V4 enabled.
Run normal image scanning operations over a period of weeks.
Observe scanner-v4-db PVC usage — grew to ~16GB within a few weeks.

Is there a retention/cleanup policy for index reports or vulnerability data in the Scanner V4 DB? If so, is it configurable?

Is this growth rate (16GB / few weeks) expected for typical scan volume, or indicative of a leak/missing vacuum/cleanup job?

Are there recommended PVC sizing guidelines based on number of images scanned or cluster size?