This topic outlines observation and troubleshooting methods you can use with Supply Chain Security Tools (SCST) - Scan components.
NoteThis topic assumes that you use SCST - Scan 1.0 because, although it is deprecated, it is still the default option in Supply Chain with Testing in this version of Tanzu Application Platform. For more information, see Add testing and scanning to your application.
VMware recommends using SCST - Scan 2.0 instead because SCST - Scan 1.0 will be removed from future versions of Tanzu Application Platform. For more information, see SCST - Scan versions.
The scans run inside a Tekton TaskRun
where the TaskRun
creates a pod. Both the TaskRun
and pod are cleaned up after completion.
Before applying a new scan, you can set a watch on the TaskRuns
, Pods
, SourceScans
, and Imagescans
to observe their progression by running:
watch kubectl get sourcescans,imagescans,pods,taskruns,scantemplates,scanpolicies -n DEV-NAMESPACE
Where DEV-NAMESPACE
is the developer namespace where the scanner is installed.