eck operator
FIPS 140-3Databases & storageElastic Cloud on Kubernetes operator for Elasticsearch, Kibana, APM, and more.
Elastic Cloud on Kubernetes operator for Elasticsearch, Kibana, APM, and more.
Pull the latest version of this image from the Ghost registry. Pulling requires authentication — generate a token and run docker login first (see Authentication below).
The Ghost catalog is public to browse, but pulling images requires an account. Generate a pull token below (or from your Account → Tokens page) — you'll get a ready-to-paste docker login command, then docker pull works.
The username is generated automatically (it looks like robot$<project>+<auto-id>, not the name you typed) and is included in the docker login command above. The secret is shown only once when you create the token.
All Ghost images are signed with cosign. Verifying the signature before deployment ensures the image has not been tampered with.
Install cosign via brew install cosign or download from the Sigstore releases page.
Reference this image in your Dockerfile as a base layer:
This is a vendor-built FIPS-enabled image: its cryptography runs on FIPS 140-3 validated modules configured by the upstream vendor. You can inspect the image metadata:
| Standard | FIPS 140-3 |
| Crypto module | Vendor-configured validated modules |
| Cryptography | Validated modules only |
| Use case | Government, regulated industries, compliance workloads |
All examples in this guide use the public image. If you've mirrored the repository for your own use (for example, to your Docker Hub namespace), update your commands to reference the mirrored image instead of the public one.
For example:
dhi/<repository>:<tag><your-namespace>/dhi-<repository>:<tag>For the examples, you may need to authenticate to the registry to pull the images.
This Docker Hardened ECK Operator image includes:
manager)/conf/eck.yaml/licenses/Replace <tag> with the image variant you want to run (e.g. 3, , , ).
3.3.13-fips3-devUse the --help flag to see usage and options:
$ docker run --rm dhi/eck-operator:<tag> --help
For deployment on Kubernetes, use the
official ECK installation guide and set the
operator image to your DHI image (e.g. dhi/eck-operator:<tag>).
Ghost hardened images come in different variants depending on their intended use. Image variants are identified by their tag.
Runtime variants are designed to run your application in production. These images are intended to be used either
directly or as the FROM image in the final stage of a multi-stage build. These images typically:
Build-time variants typically include dev in the tag name and are intended for use in the first stage of a
multi-stage Dockerfile. These images typically:
FIPS variants include fips in the variant name and tag. They come in both runtime and build-time variants. These
variants use cryptographic modules that have been validated under FIPS 140, a U.S. government standard for secure
cryptographic operations. For example, usage of MD5 fails in FIPS variants.
To view the image variants and get more information about them, select the Tags tab for this repository, and then select a tag.
To migrate to a Docker Hardened ECK Operator image, follow these steps:
Find hardened images for your app.
Inspect the image tags and choose the variant that matches your ECK major version (e.g. 2 or 3) and patch level
(e.g. 2.16.1, 3.3.1).
Update the operator image reference.
In your Helm values, Kubernetes manifests, or deployment configuration, replace the existing ECK operator image with
the DHI image (e.g. dhi/eck-operator:3 or dhi/eck-operator:2). All existing command-line arguments, environment
variables, and settings remain the same.
For multi-stage or custom Dockerfiles, use the DHI image as the runtime base. Use non-dev DHI images for the final stage that runs the operator.
Install additional packages only if needed.
The runtime image does not include a package manager. If you need extra tools, use a multi-stage build with a dev
image in the build stage and copy artifacts into the runtime stage, or use Docker Debug for ad-hoc debugging.
Runtime images do not include a shell. Use Docker Debug to attach a shell and debugging tools to a running container.
The image runs as a nonroot user by default. Ensure any mounted config or data paths are readable (and writable when required) by the container user.
The DHI image uses entrypoint /usr/local/bin/elastic-operator (normalized path) while the upstream image uses
/elastic-operator. Both execute the same binary with default command manager. This path difference is transparent to
Kubernetes deployments but may need adjustment if you override the entrypoint in custom configurations.