Chainguard Container for prometheus-operator

Minimalist Wolfi-based image for Prometheus Operator. Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes

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/prometheus-operator:latest

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

Compatibility Notes

Chainguard's prometheus-operator container image is comparable to Bitnami's Prometheus Operator image, with the following differences:

• Like all other Chainguard Images, prometheus-operator features a stripped down, minimal design
• It has few-to-zero CVEs
• It does not run as the root user

Getting started

To deploy prometheus-operator using the community Helm chart, please refer to the Helm chart documentation for comprehensive instructions, which includes supported parameters.

The following is an example of how to use the Helm chart, overriding the image with the Chainguard image:

Create a values.yaml

prometheusOperator:
  image:
    registry: cgr.dev
    repository: ORGANIZATION/prometheus-operator
    tag: latest

helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update

helm install prom-operator prometheus-community/kube-prometheus-stack \
  -f values.yaml

For full instructions on prometheus-operator, refer to the official documentation. The GitHub repository may also be useful.

Deploy a Sample Application

To illustrate how to deploy a sample application, you can use the kubectl create deployment command:

kubectl create deployment example-app \
  --image=quay.io/brancz/prometheus-example-app:v0.5.0 \
  --replicas=3 \
  --port=8080

Next, expose the application using the kubectl expose command:

kubectl expose deployment example-app \
  --port=8080 \
  --target-port=8080 \
  --name=example-app

Next, create a ServiceMonitor resource with the following servicemonitor.yaml manifest:

apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: example-app
  labels:
    team: frontend
spec:
  selector:
    matchLabels:
      app: example-app
  endpoints:
  - port: web

Apply the ServiceMonitor:

kubectl apply -f servicemonitor.yaml

Finally, create a Prometheus Resource with the following prometheus.yaml manifest. Ensure Prometheus is configured to discover the ServiceMonitor:

apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  name: prometheus
spec:
  serviceAccountName: prometheus
  serviceMonitorSelector:
    matchLabels:
      team: frontend

And apply the Prometheus resource:

kubectl apply -f prometheus.yaml

Check that Prometheus has discovered the target:

kubectl port-forward svc/prometheus-operated 9090:9090

Then, navigate to http://localhost:9090/targets in your browser. You will see the example-app listed under the Targets section.

Documentation and Resources

• GitHub Repository
• Helm Chart
• Documentation

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.