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

docs/k8s: use pod labels for upgrades (#17059) 

* docs/helm: use pod labels for upgrades

* Grammar

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

Co-authored-by: Tom Proctor <tomhjp@users.noreply.github.com>

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

Co-authored-by: Tom Proctor <tomhjp@users.noreply.github.com>

Co-authored-by: Tom Proctor <tomhjp@users.noreply.github.com>
This commit is contained in:
Jason O'Donnell 2022-09-08 11:13:11 -04:00 committed by GitHub
parent 403fdd77be
commit ced0109c41
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
website/content/docs/platform/k8s/helm/run.mdx
View File

@ -437,11 +437,20 @@ $ kubectl delete pod <name of Vault pod>
```
If Vault is deployed using `ha` mode, the standby pods must be upgraded first.
To identify which pod is currently the active primary, run the following command
on each Vault pod:
Vault has K8s service discovery built in (when enabled in the server configuration) and
will automatically change the labels of the pod with its current leader status. These labels
can be used to filter the pods.
For example, select all pods that are Vault standbys:
```shell-session
$ kubectl exec -ti <name of pod> -- vault status | grep "HA Mode"
$ kubectl get pods -l vault-active=false
```
Select the active Vault pod:
```shell-session
$ kubectl get pods -l vault-active=true
```
Next, delete every pod that is not the active primary: