bank-vaults-vault-operator

packaged by Chainguard

Chainguard Container for bank-vaults-vault-operator

Bank-Vaults' Kubernetes operator that manages HashiCorp Vault deployments and configurations.

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/bank-vaults-vault-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

The bank-vaults-vault-operator image is comparable to the upstream ghcr.io/bank-vaults/vault-operator image. Switching to the Chainguard bank-vaults-vault-operator image should not require any changes to your existing setup.

Getting Started

The upstream Helm chart at oci://ghcr.io/bank-vaults/helm-charts/vault-operator deploys the operator. Override image.repository via a values.yaml:

image:
  repository: cgr.dev/ORGANIZATION/bank-vaults-vault-operator
  tag: latest

helm install vault-operator oci://ghcr.io/bank-vaults/helm-charts/vault-operator \
  --namespace vault-system --create-namespace --wait \
  -f values.yaml

Deploying a Vault instance

The operator reconciles Vault custom resources into a running HashiCorp Vault. The Vault pod's bank-vaults sidecar needs RBAC to manage the unseal Secret — apply a ServiceAccount named vault with secrets: * and pods: get/update/patch (see the upstream rbac.yaml).

A minimal Vault CR with file storage, a KV-v2 secret engine and a policy:

apiVersion: vault.banzaicloud.com/v1alpha1
kind: Vault
metadata:
  name: vault
spec:
  size: 1
  image: cgr.dev/ORGANIZATION/vault:latest
  configPath: /etc/vault
  serviceAccount: vault
  statsdDisabled: true
  unsealConfig:
    kubernetes:
      secretName: vault-unseal-keys
  config:
    disable_mlock: true
    storage:
      file: { path: /vault/file }
    listener:
      tcp: { address: 0.0.0.0:8200, tls_disable: true }
    api_addr: http://vault:8200
  externalConfig:
    policies:
      - name: allow_secrets
        rules: |
          path "secret/*" {
            capabilities = ["create", "read", "update", "delete", "list"]
          }
    secrets:
      - type: kv
        path: secret
        options: { version: 2 }
  volumes:
    - name: vault-file
      emptyDir: {}
  volumeMounts:
    - name: vault-file
      mountPath: /vault/file

Apply it and wait for the operator to bootstrap + unseal Vault:

kubectl apply -f vault.yaml
kubectl wait --for=condition=Ready pod/vault-0 --timeout=300s

Interacting with the Vault instance

The operator stores the root token and unseal keys in the configured Secret (vault-unseal-keys above). Fetch the root token and exec into the Vault container:

ROOT_TOKEN=$(kubectl get secret vault-unseal-keys -o jsonpath='{.data.vault-root}' | base64 -d)

# Verify the policy applied by externalConfig
kubectl exec vault-0 -c vault -- env VAULT_TOKEN="$ROOT_TOKEN" VAULT_ADDR=http://127.0.0.1:8200 \
  vault policy list

# Write and read a secret
kubectl exec vault-0 -c vault -- env VAULT_TOKEN="$ROOT_TOKEN" VAULT_ADDR=http://127.0.0.1:8200 \
  vault kv put secret/demo password=s3cret_password_value
kubectl exec vault-0 -c vault -- env VAULT_TOKEN="$ROOT_TOKEN" VAULT_ADDR=http://127.0.0.1:8200 \
  vault kv get secret/demo

For richer Vault CR configurations (Raft HA, cloud KMS unseal, external auth backends, startup secrets), see the upstream examples directory.

Documentation and Resources

• Bank-Vaults operator documentation
• Bank-Vaults vault-operator GitHub repository
• Vault CR examples
• Helm chart values reference

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system 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 development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

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.