starboard-exporter

packaged by Chainguard

Chainguard Container for starboard-exporter

Starboard Exporter exposes Kubernetes security reports as Prometheus metrics.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/starboard-exporter:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This image is compatible with the upstream gsoci.azurecr.io/giantswarm/starboard-exporter image. It preserves the /manager entrypoint, default user and group 65532:65532, and /home/nonroot working directory. Starboard Exporter reads existing Kubernetes security reports; it does not perform scans.

The image supports AMD64 and ARM64. The upstream Helm chart currently restricts scheduling to AMD64 nodes. Its Pod security context selects user and group 1000:1000, which the image supports.

Prerequisites

For the upstream Helm chart example below, you need a Kubernetes cluster with AMD64 nodes, Helm, and registry credentials that allow the cluster to pull cgr.dev/ORGANIZATION/starboard-exporter. Install Chainguard's trivy-operator image and its report CRDs before deploying the exporter. Existing reports provide the data exposed as metrics.

Getting Started

Add the upstream Helm repository:

helm repo add giantswarm https://giantswarm.github.io/default-catalog
helm repo update

Replace ORGANIZATION with your Chainguard organization in this values.yaml file:

cat > values.yaml <<'EOF'
registry:
  domain: cgr.dev
image:
  name: ORGANIZATION/starboard-exporter
  tag: latest
verticalPodAutoscaler:
  enabled: false
EOF

Deploy the exporter and wait for it to become ready:

helm upgrade --install starboard-exporter giantswarm/starboard-exporter \
  --namespace starboard-exporter --create-namespace -f values.yaml
kubectl -n starboard-exporter rollout status deployment/starboard-exporter --timeout=180s

To inspect the metrics locally, keep this command running in one terminal:

kubectl -n starboard-exporter port-forward service/starboard-exporter 8080:8080

In a second terminal, fetch the Prometheus metrics:

curl --fail http://localhost:8080/metrics

The response contains runtime metrics and metrics derived from the security reports in the cluster. See the upstream documentation for supported reports and metric labels.

Configuration

The verticalPodAutoscaler.enabled: false override lets you deploy without the Vertical Pod Autoscaler CRDs. Remove it if you have installed VPA and want the chart to manage the exporter's resource requests.

Documentation and Resources

• Starboard Exporter
• Upstream Helm Chart
• Chainguard Academy

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.