luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

doc: add note about versions for helm upgrades (#8960) 

* doc: add note about versions for helm upgrades

* Fix repo search output

* Update website/pages/docs/platform/k8s/helm/run.mdx

Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>

Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
This commit is contained in:
Jason O'Donnell 2020-05-08 16:56:39 -04:00 committed by GitHub
parent 62ec73340c
commit 656685a253
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/pages/docs/platform/k8s/helm/run.mdx
View File

@ -388,6 +388,9 @@ well.
#### Upgrading Vault Servers
!> **IMPORTANT NOTE:** Helm will install the latest chart found in a repo by default.
It's recommended to specify the chart version when upgrading.
To initiate the upgrade, set the `server.image` values to the desired Vault
version, either in a values yaml file or on the command line. For illustrative
purposes, the example below uses `vault:123.456`.
@ -399,15 +402,22 @@ server:
tag: '123.456'
```
Next, list the Helm versions and choose the desired version to install.
```bash
helm search repo hashicorp/vault
NAME CHART VERSION APP VERSION DESCRIPTION
hashicorp/vault 0.5.0 Install and configure Vault on Kubernetes.
```
Next, test the upgrade with `--dry-run` first to verify the changes sent to the
Kubernetes cluster.
```bash
$ helm upgrade vault hashicorp/vault \
$ helm upgrade vault hashicorp/vault --version=0.5.0 \
--set='server.image.repository=vault' \
--set='server.image.tag=123.456' \
--dry-run
...
```
This should cause no changes (although the resources are updated). If