Announcements
- starboard-exporter now supports kubescape! In addition to Trivy VulnerabilityReports, starboard-exporter now also supports reconciliation of Kubescape VulnerabilityManifests. Metrics have been updated to include a
scannerlabel, indicating the source type of the data. Trivy and Kubescape can be used simultaneously, or individually toggled on and off. See the README for more information. - There is a breaking change to one of the CLI flags in this version. The
--vulnerability-scans-enabledflag has been renamed to--trivy-vulnerability-scans-enabledin order to facilitate the new Kubescape scanner support. Users installing via the Helm chart are not affected.
Added
- Support for Kubescape vulnerability scanning via
VulnerabilityManifestCR. - Scanner label (
scanner="trivy"orscanner="kubescape") to all vulnerability metrics to distinguish between scanning sources. - Command-line flag
--kubescape-vulnerability-scans-enabled. - Helm values configuration for enabling/disabling individual scanners under
exporter.vulnerabilityReports.scanners. - Added backwards compatibility for legacy
vulnerabilityReports.enabledHelm value (now enables Trivy scanner)
Changed
- Renamed Trivy-specific functions and constants to include “Trivy” prefix to distinguish them from Kubescape components while maintaining shared metrics.
- Command-line flag
--vulnerability-scans-enabledto--trivy-vulnerability-scans-enabled(Breaking Change).