mongodb-kubernetes-readinessprobe

packaged by Chainguard

Chainguard Container for mongodb-kubernetes-readinessprobe

Chainguard's MongoDB Kubernetes readinessprobe image provides the readiness probe that the MongoDB Controllers for Kubernetes (MCK) operator copies into each MongoDB pod to report when the MongoDB Agent has reached its goal state.

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/mongodb-kubernetes-readinessprobe:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's MongoDB Kubernetes readinessprobe image is comparable to the upstream mongodb-kubernetes-readinessprobe image.

This image is not a standalone service. The MongoDB Controllers for Kubernetes (MCK) operator schedules it as the mongodb-agent-readinessprobe init container of every MongoDB pod, and its only job is to hand the probe binary over to the MongoDB Agent container through a shared volume:

cp /probes/readinessprobe /opt/scripts/readinessprobe

To keep that working, the probe is published at the upstream path /probes/readinessprobe (a symlink to /usr/bin/readinessprobe), and the image includes coreutils to provide cp.

The probe itself reads the MongoDB Agent health status file named by AGENT_STATUS_FILEPATH, writes its own log to the file named by LOG_FILE_PATH (/var/log/mongodb-mms-automation/readiness.log when unset), and builds an in-cluster Kubernetes client, so it only runs meaningfully inside a pod.

Note that upstream versions this component independently of the operator, in the readinessProbeVersion field of release.json rather than with a Git tag, so its version does not track the operator's.

Getting Started

Point the operator at this image when you deploy it, using the READINESS_PROBE_IMAGE environment variable:

READINESS_PROBE_IMAGE=cgr.dev/ORGANIZATION/mongodb-kubernetes-readinessprobe:latest

With the mongodb-kubernetes Helm chart, set the same thing in a values.yaml:

registry:
  readinessProbe: cgr.dev/ORGANIZATION
readinessProbe:
  name: mongodb-kubernetes-readinessprobe

Then install the chart:

helm repo add mongodb https://mongodb.github.io/helm-charts
helm repo update
helm install mongodb-kubernetes mongodb/mongodb-kubernetes --values values.yaml

The operator then injects the init container into each MongoDB pod it creates; there is nothing to deploy on its own.

Documentation and Resources

• MongoDB Controllers for Kubernetes (MCK) GitHub project
• MongoDB Kubernetes Operator documentation
• MongoDB Helm charts

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.