DirectorySecurity Advisories
Sign In
Directory
vault-csi-provider logo

vault-csi-provider

Last changed

Create your Free Account

Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.

Sign Up
Versions
Overview
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Image for vault-csi-provider

HashiCorp Vault Provider for Secret Store CSI Driver

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/vault-csi-provider:latest

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

Using Vault CSI Provider

The vault-csi-provider image contains the vault-csi-provider binary. The image is intended to be a drop-in replacement for the upstream hashicorp/vault-csi-provider image.

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"
    # 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"
    # 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"
    # NOTE: "latest" tag should be replaced with specific tag for version of vault-csi-provider to use
    tag: "latest"
# other values for Vault
# ...

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.

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

Differences to openbao/openbao image

This image is not 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)

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.

Licenses

Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:

  • BUSL-1.1

  • 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

Category
application

Safe Source for Open Sourceâ„¢
Media KitContact Us
© 2024 Chainguard. All Rights Reserved.
Private PolicyTerms of Use

Product

Chainguard Images