eck-operator-fips

Fips

Stig

Utils

Updated 4 days ago

ECK Operator FIPS Overview

Secure your stack with a hardened ECK Operator 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.

Use the ECK (Elastic Cloud on Kubernetes) Operator to run Elasticsearch, Kibana, and other Elastic Stack components on Kubernetes. ECK Operator greatly simplifies deployment and operation of the Elastic Stack on Kubernetes clusters.

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

Take the Minimus ECK Operator image for a test run with Helm.

First, add the Elastic Helm chart repository to your Helm client and update the local repository index:

helm repo add elastic https://helm.elastic.co
helm repo update

Deploy the ECK Operator container image from Minimus:

helm install elastic-operator elastic/eck-operator \
  --namespace elastic-system \
  --create-namespace \
  --set=image.repository=reg.mini.dev/eck-operator-fips \
  --set=image.tag=latest

Wait for the pod to become ready:

kubectl wait -n elastic-system \
  --for=condition=Ready pod \
  -l app.kubernetes.io/name=elastic-operator \
  --timeout=60s

You are now ready to deploy an Elasticsearch cluster using the official guide.

Technical Considerations

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

ECK Operator FIPS built by Minimus:

Runs as non-root by default as user 1000. By comparison, the public image runs as user 65532.
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.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

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.