What steps did you take and what happened:

1. Deployed a container with a massive number of vulnerabilities, causing a vulnerability report that is too large to write to etcd.
2. Operator fails to write to etcd (as expected), but scan job never goes away.

What did you expect to happen:

Scan job is cleaned up despite failure to write to etcd.

Anything else you would like to add:

scanJobTTL could have been used as a workaround, but now all scan jobs are respecting the TTL set, so it would make the normal jobs hang out for that length of time as well, taking up scanning slots much longer than they need to.

Environment:

• Trivy-Operator version (use trivy-operator version): 0.29.0
• Kubernetes version (use kubectl version): 1.31.4
• OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): RHEL9