mariadb-iamguarded-fips

Chainguard Container for mariadb-iamguarded-fips

MariaDB IAMGuarded is a FIPS-compliant, security-enhanced variant of MariaDB.

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/mariadb-iamguarded-fips:latest

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

Chainguard Container for mariadb-iamguarded-fips

MariaDB IAMGuarded is a FIPS-compliant, security-enhanced variant of MariaDB.

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/mariadb-iamguarded-fips:latest

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

Overview

MariaDB IAMGuarded is a FIPS-compliant, security-enhanced variant of MariaDB designed to be deployed using its companion IAMGuarded Helm chart. This image and chart combination provides Kubernetes-native deployment patterns, secure defaults, optional metrics integration, and compatibility-tested image digests.

Deployment and Configuration

This section outlines the required configuration, optional features, and verification steps when deploying this image via the Helm chart. The chart provides security-minded defaults that are sensible but may not be production-ready for all use cases. Review the chart's values.yaml (run helm show values) for the full range of configuration options.

Prerequisites

• Kubernetes 1.24+
• Helm 3.8+
• Access to Chainguard's private registry (cgr.dev)

Registry Authentication

Access to the mariadb-iamguarded image requires authentication to Chainguard’s private registry (cgr.dev). Ensure your cluster has appropriate image pull credentials configured before installing the chart.

For detailed instructions on configuring authentication and pull credentials, see:

How to Use Chainguard Helm Charts

Required Configuration

When deploying this image via the Helm chart, the global.org value is required and specifies your Chainguard organization namespace in the registry:

global:
  org: ORGANIZATION

This value determines which private repository the mariadb-iamguarded image is pulled from.

Image Configuration

By default, the Helm chart pulls the mariadb-iamguarded image from cgr.dev using your configured organization. You may optionally override the image repository or pin to a specific digest.

Pinning to a digest is strongly recommended to prevent unexpected image updates:

image:
  registry: cgr.dev
  repository: ORGANIZATION/mariadb-iamguarded-fips
  digest: sha256:...

Optional Features

When deployed via the Helm chart, this image can be configured with several optional components and customizations.

Custom Registry Mirror

To use an internal registry mirror:

global:
  imageRegistry: myregistry.example.com
  org: ORGANIZATION

Enabling Prometheus Metrics

The Helm chart can deploy a Prometheus mysqld_exporter alongside this image to expose database metrics:

metrics:
  enabled: true
  image:
    registry: cgr.dev
    repository: ORGANIZATION/prometheus-mysqld-exporter-iamguarded-fips

Metrics are exposed on port 9104.

Enabling Volume Permissions Init Container

If your storage backend requires explicit permission adjustments, enable the volume permissions init container:

volumePermissions:
  enabled: true
  image:
    registry: cgr.dev
    repository: ORGANIZATION/os-shell-iamguarded-fips

Database Authentication

The Helm chart configures authentication for the mariadb-iamguarded-fips image. You may provide credentials directly or reference an existing Kubernetes secret.

Example:

auth:
  rootPassword: "strong-root-password"
  database: my_database
  username: app_user
  password: "strong-app-password"

For production deployments, consider sourcing credentials from an existing secret:

auth:
  existingSecret: my-mariadb-secret

By default, credentials are mounted as files instead of environment variables (auth.usePasswordFiles: true). See the chart’s values.yaml for the full set of authentication options.

Verifying and Connecting

After installation via the Helm chart, retrieve the root password from the generated Kubernetes secret:

ROOT_PASSWORD=$(kubectl get secret mariadb -n mariadb -o jsonpath='{.data.mariadb-root-password}' | base64 -d)

Connect using a temporary MariaDB client pod:

kubectl run mariadb-client --rm -it \
  --image cgr.dev/ORGANIZATION/mariadb-iamguarded-fips \
  --restart=Never -n mariadb -- \
  mariadb -h mariadb.mariadb.svc.cluster.local -u root -p"$ROOT_PASSWORD"

If metrics are enabled, verify Prometheus exposure:

kubectl port-forward svc/mariadb 9104:9104 -n mariadb
curl http://localhost:9104/metrics | grep mysql_up

Documentation and Resources

• MariaDB Official Documentation
• MariaDB Knowledge Base
• Prometheus mysqld Exporter

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.