Update vault-helm to 0.2.1 (#7873)
This commit is contained in:
parent
cf31edef70
commit
68f36d571f
|
@ -52,7 +52,7 @@ $ git clone https://github.com/hashicorp/vault-helm.git
|
|||
$ cd vault-helm
|
||||
|
||||
# Checkout a tagged version
|
||||
$ git checkout v0.2.0
|
||||
$ git checkout v0.2.1
|
||||
|
||||
# Run Helm
|
||||
$ helm install --dry-run ./
|
||||
|
@ -83,10 +83,6 @@ and consider if they're appropriate for your deployment.
|
|||
|
||||
* `server` - Values that configure running a Vault server within Kubernetes.
|
||||
|
||||
* `securityContext` - Values that configure Vault pods security context.
|
||||
|
||||
- `readOnlyRootFilesystem` (`boolean: true`) - When set to `true`, the root filesystem of the container is read only.
|
||||
|
||||
* `resources` (`string: null`) - The resource requests and limits (CPU, memory, etc.) for each of the server. This should be a multi-line string mapping directly to a Kubernetes [ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#resourcerequirements-v1-core) object. If this isn't specified, then the pods won't request any specific amount of resources. **Setting this is highly recommended.**
|
||||
|
||||
```yaml
|
||||
|
|
|
@ -60,7 +60,7 @@ $ git clone https://github.com/hashicorp/vault-helm.git
|
|||
$ cd vault-helm
|
||||
|
||||
# Checkout a tagged version
|
||||
$ git checkout v0.2.0
|
||||
$ git checkout v0.2.1
|
||||
|
||||
# Run Helm
|
||||
$ helm install --name vault ./
|
||||
|
|
Loading…
Reference in New Issue