open-policy-agent-fake-reader

packaged by Chainguard

Chainguard Container for open-policy-agent-fake-reader

A sidecar component for OPA Gatekeeper that reads audit log files and exposes them for external log monitoring systems.

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/open-policy-agent-fake-reader: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 ghcr.io/open-policy-agent/fake-reader image. Switching to Chainguard's open-policy-agent-fake-reader image should not require any changes to your existing setup.

FIPS support

Chainguard's open-policy-agent-fake-reader-fips image ships with a validated redistribution of the OpenSSL FIPS provider module. For more on FIPS support in Chainguard container images, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Usage Instructions

fake-reader is a companion utility for Gatekeeper, OPA's policy controller for Kubernetes. It reads audit violation logs exported to disk via Gatekeeper's export system, which writes .log files to a configurable path (default: /tmp/violations/topics).

Deploying with Gatekeeper

Install Gatekeeper via Helm, then deploy fake-reader as a sidecar or standalone pod alongside it:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: fake-reader
  namespace: gatekeeper-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app: fake-reader
  template:
    metadata:
      labels:
        app: fake-reader
    spec:
      containers:
        - name: fake-reader
          image: cgr.dev/ORGANIZATION/open-policy-agent-fake-reader:latest
          volumeMounts:
            - name: violations
              mountPath: /tmp/violations/topics
      volumes:
        - name: violations
          emptyDir: {}

Configuring the Export Connection

Apply the Gatekeeper Connection resource to enable disk-based audit export:

kubectl apply -f https://raw.githubusercontent.com/open-policy-agent/gatekeeper/master/test/export/fake-reader/export_connection.yaml

Or inline:

apiVersion: connection.gatekeeper.sh/v1alpha1
kind: Connection
metadata:
  name: audit-connection
  namespace: gatekeeper-system
spec:
  driver: "disk"
  config:
    path: "/tmp/violations/topics"
    maxAuditResults: 3
    closedConnectionTTL: "1m"

Once the connection is active, Gatekeeper writes violation .log files to the configured path and fake-reader reads them every 90 seconds.

Documentation and Resources

• Gatekeeper Documentation
• Exporting Data with Gatekeeper
• fake-reader Source
• Project Repository

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.