Provenance Collector
The Provenance Collector is a Nebari Software Pack that produces
compliance-grade supply-chain reports for every container image and Helm
release running on a Kubernetes cluster. It is deployed by the
Nebari Operator as part of
Nebari Infrastructure Core (NIC), runs on a schedule as a CronJob, and ships
each timestamped JSON report to a web dashboard, a shared PVC, or a ConfigMap.
It exists because answering “what is actually running on this cluster, where did it come from, and is it signed?” should not require manual auditing.
What it does
Section titled “What it does”| Capability | Description |
|---|---|
| Image discovery | Scans all pods across namespaces, deduplicates by workload owner |
| Digest resolution | Resolves every image tag to its immutable SHA256 digest |
| Signature verification | Checks for cosign signatures (existence or key-based verification) |
| SLSA provenance | Detects SLSA provenance attestations via the OCI referrers API |
| SBOM detection | Detects attached SPDX / CycloneDX attestations |
| Update checking | Compares running tags against the latest semver tags |
| Helm release tracking | Discovers all deployed Helm releases with chart versions |
| Web dashboard | Optional UI with filters, sorting, and an image detail panel |
| Grafana integration | JSON API compatible with the Infinity datasource |
Guides
Section titled “Guides”- Quick Start — install the collector and view your first report.
- Architecture — how the collector, dashboard, and frontend fit together.
- Storage Modes — choosing between
http,pvc, andconfigmap. - Web Dashboard — the UI, its JSON API, and Grafana integration.
Reference
Section titled “Reference”- Configuration — every environment variable and its chart value.
- Report Schema — the JSON output structure.
- NebariApp CRD — operator integration fields.
Status: Under active development as part of NIC. APIs, chart values, and report schema may change without notice while pre-1.0.
Additional deployment examples (standalone, Nebari, ArgoCD) live in the
examples/
directory of the repository.