Chainguard Container for vault-secrets-operator

Vault Secrets Operator (VSO) allows Pods to consume Vault secrets natively from Kubernetes Secrets.

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-secrets-operator:latest

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

Compatibility Notes

Chainguard's Vault Secrets Operator image contains the vault-secrets-operator binary. The image is intended to be a drop-in replacement for the hashicorp/vault-secrets-operator image.

This image is not identical to the hashicorp/vault-secrets-operator image. In particular:

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

Getting Started

Chainguard's Vault Secrets Operator image is not meant to be run as standalone and has to be run inside a Kubernetes cluster.

The Chainguard Vault Secrets Operator image is meant to be used with the hashicorp/vault-secrets-operator Helm chart, and in conjunction with the Hashicorp Vault deployment.

To use the Chainguard image, configure the hashicorp/vault-secrets-operator Helm chart to the specify the image in a values.yaml file:

controller:
  manager:
    image:
      # NOTE: replace the ORGANIZATION with name used for your organization within the Chainguard registry
      repository: "cgr.dev/ORGANIZATION/vault-secrets-operator"
      # NOTE: "latest" tag should be replaced with specific tag for version of vault-secrets-operator to use
      tag: "latest"
# other values to configure Vault Secrets Operator

The Vault Secrets Operator Installation documentation provides step-by-step instructions for installing the Vault Secrets Operator and configuring Vault to allow Kubernetes-based authentication.

Documentation and Resources

• Vault Secrets Operator Documentation
• Vault Secrets Operator Tutorial
• hashicorp/vault-secrets-operator GitHub Repository

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.