Chainguard Container for vault-csi-provider-fips

HashiCorp Vault Provider for Secret Store CSI Driver

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/vault-csi-provider-fips:latest

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

Compatibility notes

This FIPS-Compliant image is compatible with the HashiCorp Vault CSI Provider image. Switching to Chainguard's image should not require any changes to your existing configuration. By default, this image runs as a non-root user, with temporary root privileges enabled for specific needs like communicating with a privileged socket.

Differences to hashicorp/vault-csi-provider image

This image is not completely identical to the hashicorp/vault-csi-provider image. In particular:

• The vault-csi-provider binary is stored in /usr/bin, with symlink to the binary placed in /bin for compatibility
• The underlying OS is Wolfi (which is glibc based) whereas the Hashicorp image uses Alpine (which is musl based)

Getting started

Using Vault CSI Provider

The image is not meant to be run as standalone and has to be run inside a Kubernetes cluster. Vault CSI Provider image is meant to be used as part of Hashicorp Vault deployment, using the hashicorp/vault Helm chart.

To use the Chainguard image, configure the hashicorp/vault Helm chart to enable the specify the image in the values. Such as:

# disable vault-agent injection
injector:
  enabled: false
csi:
  enabled: true
  image:
    # NOTE: replace the ORGANIZATION with name used for your organization within the Chainguard registry
    repository: "cgr.dev/ORGANIZATION/vault-csi-provider-fips"
    # NOTE: "latest" tag should be replaced with specific tag for version of vault-csi-provider to use
    tag: "latest"
# other values for Vault
# ...

It is recommended to also use Chainguard images for vault and vault-k8s images - for example:

# disable vault-agent injection
injector:
  enabled: false
csi:
  enabled: true
  image:
    # NOTE: replace the ORGANIZATION with name used for your organization within the Chainguard registry
    repository: "cgr.dev/ORGANIZATION/vault-csi-provider-fips"
    # NOTE: "latest" tag should be replaced with specific tag for version of vault-csi-provider to use
    tag: "latest"
server:
  image:
    # NOTE: replace the ORGANIZATION with name used for your organization within the Chainguard registry
    repository: "cgr.dev/ORGANIZATION/vault-fips" # FIPS compliant variant
    # NOTE: "latest" tag should be replaced with specific tag for version of vault-csi-provider to use
    tag: "latest"
# other values for Vault
# ...

NOTE: Secrets Store CSI Driver first needs to be installed in the cluster before adding the Vault CSI Provider.

Documentation and resources

The Vault CSI Provider Installation document provides a step-by-step instruction for installing the Vault CSI Provider and configuring Vault to allow Kubernetes-based authentication.

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.