1. Images & Charts
  2. prometheus-operator-fips
prometheus-operator-fips

prometheus-operator-fips

Fips
Infra
Stig
Updated 9 hours ago

Prometheus-Operator-FIPS Overview

Secure your stack with a FIPS-validated, hardened Prometheus Operator image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies.


The Prometheus Operator is a Kubernetes operator used to deploy, manage, and scale Prometheus-based monitoring inside a Kubernetes cluster.


FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.


Try It Out

For a quick test, print the help menu:

docker run --rm \
reg.mini.dev/prometheus-operator-fips --help

Ready to Deploy using a Helm chart?

Prerequisites

  • A running Kubernetes cluster (v1.21 or higher is recommended)
  • Helm v3.8 or higher for OCI support (Installation instructions)
  • kubectl installed and configured

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Add Repository to your Local Client

Add the official Helm chart repository to your local Helm client.

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

Step 3: Install Prometheus-Operator

helm install prometheus-stack prometheus-community/kube-prometheus-stack \
  -n monitoring \
  --create-namespace \
  --wait \
  --set=prometheusOperator.image.registry=reg.mini.dev \
  --set=prometheusOperator.image.repository=prometheus-operator-fips \
  --set=prometheusOperator.image.tag=latest \

Check that all Pods are up and running:

kubectl get pods -n monitoring

Step 4: Deploy Example App

Deploy the example-app and create a PodMonitor:

cat <<EOF | kubectl apply -f -
apiVersion: apps/v1
kind: Deployment
metadata:
  name: example-app
spec:
  replicas: 3
  selector:
    matchLabels:
      app: example-app
  template:
    metadata:
      labels:
        app: example-app
    spec:
      containers:
      - name: example-app
        image: ghcr.io/rhobs/prometheus-example-app:0.4.2
        ports:
        - name: web
          containerPort: 8080
---
apiVersion: monitoring.coreos.com/v1
kind: PodMonitor
metadata:
  name: example-app
  labels:
    release: prometheus-stack # Must be identical to the Helm release above
spec:
  selector:
    matchLabels:
      app: example-app
  podMetricsEndpoints:
  - port: web
    path: /metrics
EOF

Note that this example uses ghcr.io/rhobs/prometheus-example-app:0.4.2 instead of the more common quay.io/brancz/prometheus-example-app:v0.5.0 because the latter is only compiled for amd64 (ref).

Step 5: Make Prometheus Accessible

kubectl port-forward -n monitoring svc/prometheus-stack-kube-prom-prometheus 9090:9090

Check the health of the target:

curl -sS --fail-with-body "http://127.0.0.1:9090/api/v1/targets" | \
  jq -r '.data.activeTargets[] | select(.labels.container == "example-app")'

Technical Considerations

The Prometheus-Operator-FIPS image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Prometheus-Operator-FIPS built by Minimus:

  1. Runs as non-root by default as user 1000. The public image runs as user 65534 by default.
  2. Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.


Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.