Chainguard Container for influxdb-iamguarded

InfluxDB is a time series database designed to handle high write and query loads.

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

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

Overview

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.

Helm Chart Installation

The InfluxDB IAMGuarded Helm chart is delivered exclusively through the same OCI registry as your Chainguard images:

cgr.dev/$ORGANIZATION/iamguarded-charts/influxdb

Basic Installation

Once authenticated (see below) you can install the chart with standard Helm commands and your organization name:

helm install influxdb oci://cgr.dev/$ORGANIZATION/iamguarded-charts/influxdb \
  --set "global.org=$ORGANIZATION"

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.

Configuration Requirements

Organization Setting

The global.org value is required and can be set either:

• Via --set flag during installation
• In your existing values.yaml file

Registry Configuration

For users who mirror images to custom repositories:

• Use global.imageRegistry to override the default cgr.dev
• For complex mirroring strategies, consult the chart's values.yaml for individual image configuration options including registry, repository, tag, and digest

Example values.yaml for individual image configuration:

# Main InfluxDB server image
image:
  registry: myregistry.example.com
  repository: mirrored/influxdb-iamguarded
  digest: sha256:... # Use specific digest instead of tag

# OS Shell image for volume permissions
volumePermissions:
  enabled: true
  image:
    registry: myregistry.example.com
    repository: mirrored/os-shell-iamguarded
    digest: sha256:... # Use specific digest instead of tag

# Backup provider images
backup:
  uploadProviders:
    google:
      image:
        registry: myregistry.example.com
        repository: mirrored/google-cloud-sdk-iamguarded
        digest: sha256:...
    azure:
      image:
        registry: myregistry.example.com
        repository: mirrored/az-iamguarded
        digest: sha256:...
    aws:
      image:
        registry: myregistry.example.com
        repository: mirrored/aws-cli-iamguarded
        digest: sha256:...

Authentication

Ensure proper pull credentials are configured through one of the following methods:

Option 1: Using Helm values with global.imagePullSecrets

# values.yaml
global:
  imagePullSecrets:
    - name: chainguard-pull-secret

Option 2: Create a Kubernetes pull secret

# Step 1: Authenticate with chainctl and generate a pull token
chainctl auth login
chainctl auth configure-docker --pull-token --save --ttl=24h

# Step 2: Create the Kubernetes secret
kubectl create secret docker-registry chainguard-pull-secret \
  --docker-server=cgr.dev \
  --docker-username=$(echo cgr.dev | docker-credential-cgr get | jq -r '.Username') \
  --docker-password=$(echo cgr.dev | docker-credential-cgr get | jq -r '.Secret') \
  -n <your-namespace>

# Step 3: Reference the secret in your Helm installation
helm install influxdb oci://cgr.dev/$ORGANIZATION/iamguarded-charts/influxdb \
  --set "global.org=$ORGANIZATION" \
  --set "global.imagePullSecrets[0].name=chainguard-pull-secret"

Option 3: Cluster node-scoped registry permissions (cluster-dependent)

Default Configuration

The chart comes with sensible defaults for InfluxDB IAMGuarded:

• Admin user: Automatically created with username admin
• Organization: Default organization primary is created
• Bucket: Default bucket primary is created
• Authentication: HTTP authentication is enabled by default
• Persistence: 10Gi persistent volume claim for data storage

Best Practices

1. Pin to Digest: While charts follow the same tagging scheme as Chainguard images, always pin to a specific chart digest to prevent unexpected updates:

   helm install influxdb oci://cgr.dev/$ORGANIZATION/iamguarded-charts/influxdb@sha256:DIGEST \
     --set "global.org=$ORGANIZATION"

   The digest can be found in the output of helm pull e.g:

   helm pull oci://cgr.dev/$ORGANIZATION/iamguarded-charts/influxdb
   Pulled: cgr.dev/ORGANIZATION/iamguarded-charts/influxdb:2.7.11
   Digest: sha256:6471bd888adc895c4c8d259fd72ae7d165da585208bf5670228319c8c0872a49

2. 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.

3. Image Pinning: All IAMGuarded charts pin images to specific digests that have been tested for compatibility, ensuring reliable deployments.

InfluxDB Features

This image supports all standard InfluxDB v2 features including:

• Time Series Database: Optimized for time-stamped data storage and retrieval
• Flux Query Language: Powerful data scripting and query language
• API Compatible: Full compatibility with InfluxDB v2 API
• Multi-organization Support: Isolated tenants within the same instance
• Token-based Authentication: Secure API access with fine-grained permissions
• Backup and Restore: Built-in backup capabilities with cloud provider support

Prerequisites

Prerequisites are defined in the chart's Chart.yaml and individual templates. No additional requirements beyond standard Kubernetes and Helm functionality are needed.

Security Considerations

The InfluxDB IAMGuarded chart provides security-minded defaults while acknowledging the cluster-specific nature of both InfluxDB and Kubernetes environments. Key security features include:

• Non-root execution: Runs as non-root user by default
• Minimal attack surface: Based on Chainguard's hardened base images
• Regular updates: Daily rebuilds ensure latest security patches
• SBOM included: Full software bill of materials for compliance

For detailed configuration options and advanced usage, refer to the chart's values.yaml file.

Direct Container Usage

While we recommend using the Helm chart for production deployments, the container can be run directly for testing:

docker run -p 8086:8086 \
  -e INFLUXD_HTTP_AUTH_ENABLED=true \
  -e INFLUXD_ADMIN_USER=admin \
  -e INFLUXD_ADMIN_PASSWORD=supersecret \
  -e INFLUXD_ADMIN_ORG=myorg \
  -e INFLUXD_ADMIN_BUCKET=mybucket \
  cgr.dev/ORGANIZATION/influxdb-iamguarded:latest

Note: For production use, always deploy using the Helm chart which provides proper secrets management, persistence, and security configurations.

What are Chainguard Containers?

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:

• 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 -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.

Learn More

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.

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.