Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Request trialInfluxDB is a time series database designed to handle high write and query loads.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
InfluxDB IAMGuarded is a security-enhanced variant of InfluxDB designed to be deployed using its companion IAMGuarded Helm chart. This image and chart combination provides additional security benefits over standard InfluxDB deployments.
The InfluxDB IAMGuarded Helm chart is delivered exclusively through the same OCI registry as your Chainguard images:
Once authenticated (see below) you can install the chart with standard Helm commands and your organization name:
Important: Replace $ORGANIZATION
with your Chainguard organization name. The default organization in the chart values is chainguard-private
, which must be changed to match your organization.
The global.org
value is required and can be set either:
--set
flag during installationvalues.yaml
fileFor users who mirror images to custom repositories:
global.imageRegistry
to override the default cgr.dev
values.yaml
for individual image configuration options including registry
, repository
, tag
, and digest
Example values.yaml
for individual image configuration:
Ensure proper pull credentials are configured through one of the following methods:
Option 1: Using Helm values with global.imagePullSecrets
Option 2: Create a Kubernetes pull secret
Option 3: Cluster node-scoped registry permissions (cluster-dependent)
The chart comes with sensible defaults for InfluxDB IAMGuarded:
admin
primary
is createdprimary
is createdPin to Digest: While charts follow the same tagging scheme as Chainguard images, always pin to a specific chart digest to prevent unexpected updates:
The digest can be found in the output of helm pull
e.g:
Review Default Values: 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.
Image Pinning: All IAMGuarded charts pin images to specific digests that have been tested for compatibility, ensuring reliable deployments.
This image supports all standard InfluxDB v2 features including:
Prerequisites are defined in the chart's Chart.yaml
and individual templates. No additional requirements beyond standard Kubernetes and Helm functionality are needed.
The InfluxDB IAMGuarded chart provides security-minded defaults while acknowledging the cluster-specific nature of both InfluxDB and Kubernetes environments. Key security features include:
For detailed configuration options and advanced usage, refer to the chart's values.yaml
file.
While we recommend using the Helm chart for production deployments, the container can be run directly for testing:
Note: For production use, always deploy using the Helm chart which provides proper secrets management, persistence, and security configurations.
Chainguard Containers are minimal container images that are secure by default.
In many cases, the Chainguard Containers tagged as :latest
contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a more secure software supply chain.
The main features of Chainguard Containers include:
For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a -dev
variant.
Although the -dev
container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev
variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.
To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.
In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.
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.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
GCC-exception-3.1
GPL-2.0-only
GPL-2.0-or-later
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement