Is there a preferred way to re-run kube-bench to check changes

[spurin]

Howdy,

Great job on Kube-Bench and all that you do, thanks!

Is there a recommended approach for re-running kube-bench to check for changes? Currently I'm doing the following -

kubectl delete pod --selector=app=kube-bench; kubectl replace --force -f job.yaml

If this is okay of if there's an alternative preferred approach, it would make a nice update to the documentation. I'm happy to raise a PR accordingly. Let me know and I'll follow this up if desired.

[spurin]

This combo provided what I was looking for, again though, feedback appreciated on approach and whether this is desired for documentation updates

kubectl delete pod --selector=app=kube-bench; kubectl replace --force -f job.yaml; kubectl wait --for=condition=complete --timeout=600s job/kube-bench; kubectl logs --selector='app=kube-bench' --tail=1000 | more