Vault Csi Provider

HashiCorp Vault Provider for Secret Store CSI Driver
Alternatives To Vault Csi Provider
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Consul26,5351,0221,872a day ago782September 20, 20221,250mpl-2.0Go
Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
10 days ago21gpl-3.0Go
Modern self-hosting framework, fully automated from empty disk to operating services with a single command.
Kubernetes External Secrets2,588
a year ago10mitJavaScript
Integrate external secret management systems with Kubernetes
Bank Vaults1,86216a day ago71April 05, 2022225apache-2.0Go
A Vault swiss-army knife: a K8s operator, Go client with automatic token renewal, automatic configuration, multiple unseal options and more. A CLI tool to init, unseal and configure Vault (auth methods, secret engines). Direct secret injection into Pods.
Helm Secrets974
19 days ago1apache-2.0Shell
A helm plugin that help manage secrets with Git workflow and store them anywhere
Kubernetes Vault966
2 years ago1July 03, 2021apache-2.0Go
Use Vault to store secrets for Kubernetes!
Vault Helm920
4 days ago170mpl-2.0Shell
Helm chart to install Vault and other associated components.
2 days ago68mitGo
The Kubefirst Open Source Platform
Vault Operator733
3 years ago60apache-2.0Go
Run and manage Vault on Kubernetes simply and securely
Vault K8s701112 days ago45May 25, 202299mpl-2.0Go
First-class support for Vault and Kubernetes.
Alternatives To Vault Csi Provider
Select To Compare

Alternative Project Comparisons

HashiCorp Vault Provider for Secrets Store CSI Driver

HashiCorp Vault provider for the Secrets Store CSI driver allows you to get secrets stored in Vault and use the Secrets Store CSI driver interface to mount them into Kubernetes pods.



Using helm

The recommended installation method is via helm 3:

helm repo add hashicorp
# Just installs Vault CSI provider. Adjust `server.enabled` and `injector.enabled`
# if you also want helm to install Vault and the Vault Agent injector.
helm install vault hashicorp/vault \
  --set "server.enabled=false" \
  --set "injector.enabled=false" \
  --set "csi.enabled=true"

Using yaml

You can also install using the deployment config in the deployment folder:

kubectl apply -f deployment/vault-csi-provider.yaml


See the learn tutorial and documentation pages for full details of deploying, configuring and using Vault CSI provider. The integration tests in test/bats/provider.bats also provide a good set of fully worked and tested examples to build on.


To troubleshoot issues with Vault CSI provider, look at logs from the Vault CSI provider pod running on the same node as your application pod:

kubectl get pods -o wide
# find the Vault CSI provider pod running on the same node as your application pod

kubectl logs vault-csi-provider-7x44t

Pass -debug=true to the provider to get more detailed logs. When installing via helm, you can use --set "csi.debug=true".


The Makefile has targets to automate building and testing:

make build test

The project also uses some linting and formatting tools. To install the tools:

make bootstrap

You can then run the additional checks:

make fmt lint mod

To run a full set of integration tests on a local kind cluster, ensure you have the following additional dependencies installed:

You can then run:

make setup-kind e2e-image e2e-setup e2e-test

Finally tidy up the resources created in the kind cluster with:

make e2e-teardown
Popular Vault Projects
Popular Kubernetes Projects
Popular Security Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.