Important: Coverity Scan Services is optional.
You can optionally deploy Coverity Scan Services in the Kubernetes cluster. This enables you to run scans in the Kubernetes cluster as opposed to on the client system.
Scan Services performs a scan in two phases:
- Thin Client, installed on the client, captures the artifacts to be analyzed.
- Scan Services, installed in the Kubernetes cluster, performs the analysis.
Each scan performed by the Scan Services is identified by a unique scan identifier. Coverity Connect saves and manages scan data in the PostgreSQL database. Scan Services notifies the client of the scan status. To review and manage analyses, you can use either the Coverity API or the Coverity Connect UI.
Scan Services consists of the following services:
- Scan Service is the scan orchestrator. It provides APIs to create, retrieve, and schedule scans using Kubernetes jobs.
- Storage Service manages storage, provides APIs to create new storage objects, and provides pre-signed URLs to upload and download artifacts.
- Cache Service manages caching.