1. Images & Charts
  2. coredns-fips
coredns-fips

coredns-fips

Fips
Infra
Stig
Updated 4 days ago

CoreDNS-FIPS Overview

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


CoreDNS provides DNS-based service discovery within a Kubernetes cluster, translating service names into IP addresses so Pods can communicate reliably.


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

This guide will not install CoreDNS with Helm since Minikube already deploys CoreDNS as a core cluster component. We will update the existing Deployment instead of installing a Helm release.

Prerequisites

  • A running Kubernetes cluster (v1.21 or higher is recommended)
  • 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: Override the CoreDNS Image

kubectl -n kube-system set image deployment/coredns \
  coredns=reg.mini.dev/coredns-fips:latest

Verify the deployment:

kubectl -n kube-system rollout status deployment/coredns

Wait a minute and check that the Pod is up and running:

kubectl -n kube-system get po

Confirm that Minimus images were deployed:

kubectl -n kube-system describe pods | grep Image:

Step 3: Clean Up

Roll back using rollout history to reset Minikube to the default CoreDNS image:

kubectl -n kube-system rollout undo deployment/coredns

Verify:

kubectl -n kube-system rollout status deployment/coredns

Technical Considerations

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

CoreDNS-FIPS built by Minimus:

  1. Runs as non-root by default as user 65532. The public image runs as nonroot:nonroot.
  2. Listens on but does not expose the default port: 53/tcp and 53/udp. The public image exposes those ports by default.
  3. 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.