Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Updating Kubernetes Upgrade instructions #25285

Closed
wants to merge 1 commit into from
Closed

Updating Kubernetes Upgrade instructions #25285

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 4 additions & 1 deletion website/content/docs/platform/k8s/helm/run.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -436,7 +436,10 @@ running:
$ kubectl delete pod <name of Vault pod>
```

If Vault is deployed using `ha` mode, the standby pods must be upgraded first.
If Vault is deployed using `ha` mode, the standby pods must be upgraded first. Before deleting the pod, make sure to remove the node from the raft by running vault operator raft remove-peer <server_id>. To confirm that the node has been successfully removed from Raft, you can run vault operator raft list-peers. Only after confirming the removal should you delete the pod.

> If you remove the pod directly without properly removing the node from the cluster, Raft will be unaware of the correct number of nodes in the cluster. This can trigger a leader election, potentially causing downtime.

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.
Expand Down