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

Add some warnings to the upgrade guide

Browse source
This commit is contained in:
Jeff Mitchell 2017-06-16 13:23:22 -04:00
parent 5d54aaf10a
commit 0ea8f17357
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
website/source/docs/guides/upgrading/index.html.md
View file

@ -13,6 +13,11 @@ These are general upgrade instructions for Vault for both non-HA and HA setups.
Please ensure that you also read the version-specific upgrade notes which can be
found in the sidebar.
**Always** back up your data before upgrading! Vault does not make
backwards-compatibility guarantees for its data store. If you need to roll back
to a previous version of Vault, it is always a good idea to roll back your data
store as well.
## Non-HA Installations
Upgrading non-HA installations of Vault is as simple as replacing the Vault
@ -32,6 +37,10 @@ particular setup since HA setups can differ on whether a load balancer is in
use, what addresses clients are being given to connect to Vault (standby +
leader, leader-only, or discovered via service discovery), etc.
Whatever method you use, you should ensure that you never fail over from a
newer version of Vault to an older version. Our suggested procedure is designed
to prevent this.
Please note that Vault does not support true zero-downtime upgrades, but with
proper upgrade procedure the downtime should be very short (a few hundred
milliseconds to a second depending on how the speed of access to the storage
@ -58,7 +67,8 @@ active duty. To do this:
3. Start the node
4. Unseal the node (it will now be a standby)
Internal upgrade tasks will happen after one of the upgraded standby nodes takes over active duty.
Internal upgrade tasks will happen after one of the upgraded standby nodes
takes over active duty.
Be sure to also read and follow any instructions in the version-specific
upgrade notes.