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

New seal migration strategy doesn't work in 1.4. (#9765)

Browse source
This commit is contained in:
ncabatoff 2020-08-20 09:54:28 -04:00 committed by GitHub
parent 0a13195450
commit f20f3747c7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
website/pages/docs/concepts/seal.mdx
View file

@ -134,7 +134,7 @@ seal will require that the KMS key be accessible during the migration.
~> **NOTE**: Seal migration from KMS seal to KMS seal of same kind is not
currently supported. We plan to support this officially in a future release.
### Migration post Vault 1.4.0
### Migration post Vault 1.5.1
These steps are common for seal migrations between any supported kinds and for
any storage backend.
@ -185,7 +185,7 @@ any storage backend.
new seal information. Standby nodes can be restarted right away and the active
node can be restarted upon a leadership change.
### Migration pre 1.4
### Migration pre 1.5.1
#### Migration From Shamir to Auto Unseal