This is a forked version of HashiCorp's Vault Helm Chart. It is forked for business continuity (should the original be deleted) and to adhere to the MPL-2.0 license of public disclosure of source changes. This repository is used as a submodule in other repositories that install and setup Vault.
⚠️ Please note: We take Vault's security and our users' trust very seriously. If you believe you have found a security issue in Vault Helm, please responsibly disclose by contacting us at [email protected].
This repository contains the official HashiCorp Helm chart for installing and configuring Vault on Kubernetes. This chart supports multiple use cases of Vault on Kubernetes depending on the values provided.
For full documentation on this Helm chart along with all the ways you can use Vault with Kubernetes, please see the Vault and Kubernetes documentation.
To use the charts here, Helm must be configured for your Kubernetes cluster. Setting up Kubernetes and Helm is outside the scope of this README. Please refer to the Kubernetes and Helm documentation.
The versions required are:
- Helm 3.6+
- Kubernetes 1.22+ - This is the earliest version of Kubernetes tested. It is possible that this chart works with earlier versions but it is untested.
To install the latest version of this chart, add the Hashicorp helm repository
and run helm install:
$ helm repo add hashicorp https://helm.releases.hashicorp.com
"hashicorp" has been added to your repositories
$ helm install vault hashicorp/vaultPlease see the many options supported in the values.yaml
file. These are also fully documented directly on the
Vault website.
This Helm chart has been customized in the following ways:
The Service spec in the server-service.yaml file now allows setting a
specific IP address when the Service type is set to LoadBalancer and a
maas.lbAddress value has been provided.