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.

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

Upgrade version of Vault #801

Open
mrsimonemms opened this issue Sep 4, 2024 · 0 comments
Open

Upgrade version of Vault #801

mrsimonemms opened this issue Sep 4, 2024 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@mrsimonemms
Copy link
Contributor

mrsimonemms commented Sep 4, 2024

The version of Vault we're running at the moment is 1.11.3 (chart's target revision is 0.22.0). There is an issue in 1.11.2 where a pod going down means that it doesn't recover, which also seems to be affecting us - see details hashicorp/vault#17470

This version is quite old anyway, being released about 2 years ago and is now in the 1.17.x range. We should upgrade our version of Vault to a much newer version, but also ensure that there are no interface changes which would break our application.


In order to unseal Vault after a node restart - the pod should show 0/1 ready state...

  1. Set up port forwarding for the pod
  2. Got to the UI
  3. Find the first unseal key kubectl get secrets -n vault vault-unseal-secret -o jsonpath='{.data.root-unseal-key-1}' | base64 -d
  4. In the prompt "unseal key portion", enter the unseal key
  5. Repeat until you have all the required key portions (usually 3 parts required)
  6. Repeat for each pod
@mrsimonemms mrsimonemms added bug Something isn't working enhancement New feature or request labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant