Vault
- Vault charmers
- Security
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/edge | 383 | 23 Aug 2024 | |
latest/edge | 367 | 25 Jul 2024 | |
latest/edge | 364 | 23 Jul 2024 | |
latest/edge | 363 | 23 Jul 2024 | |
latest/edge | 336 | 20 Jun 2024 | |
latest/edge | 335 | 20 Jun 2024 | |
latest/edge | 334 | 20 Jun 2024 | |
latest/edge | 333 | 20 Jun 2024 | |
latest/edge | 332 | 20 Jun 2024 | |
latest/edge | 331 | 20 Jun 2024 | |
latest/edge | 330 | 20 Jun 2024 | |
latest/edge | 329 | 20 Jun 2024 | |
latest/edge | 220 | 20 Jan 2024 | |
latest/edge | 216 | 19 Jan 2024 | |
latest/edge | 214 | 19 Jan 2024 | |
latest/edge | 213 | 19 Jan 2024 | |
latest/edge | 109 | 18 Apr 2023 | |
latest/edge | 79 | 02 Aug 2022 | |
1.16/stable | 387 | 12 Sep 2024 | |
1.16/candidate | 387 | 12 Sep 2024 | |
1.16/beta | 387 | 12 Sep 2024 | |
1.16/edge | 393 | 21 Nov 2024 | |
1.15/stable | 357 | 24 Jul 2024 | |
1.15/candidate | 357 | 24 Jul 2024 | |
1.15/beta | 357 | 24 Jul 2024 | |
1.15/edge | 376 | 31 Jul 2024 | |
1.8/stable | 372 | 26 Jul 2024 | |
1.8/edge | 164 | 09 Aug 2023 | |
1.8/edge | 162 | 09 Aug 2023 | |
1.8/edge | 161 | 09 Aug 2023 | |
1.8/edge | 159 | 09 Aug 2023 | |
1.8/edge | 157 | 09 Aug 2023 | |
1.8/edge | 156 | 09 Aug 2023 | |
1.8/edge | 155 | 09 Aug 2023 | |
1.8/edge | 154 | 09 Aug 2023 | |
1.8/edge | 140 | 07 Aug 2023 | |
1.8/edge | 138 | 04 Aug 2023 | |
1.8/edge | 135 | 04 Aug 2023 | |
1.8/edge | 131 | 04 Aug 2023 | |
1.7/stable | 371 | 26 Jul 2024 | |
1.6/stable | 369 | 26 Jul 2024 | |
1.5/stable | 370 | 26 Jul 2024 |
juju deploy vault --channel 1.15/beta
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
Restore a backup
Pre-requisites
To restore a Vault Backup, ensure you:
- Have a Vault cluster deployed.
- Your Vault deployment is in active idle state.
- Have access to S3 storage where your backup is saved.
- Have configured the settings for S3 storage.
- Have access to the unseal keys and root-token used by the Vault cluster at the time of creating the backup.
Once the prerequisites are in place you can run the restore-backup
action on the leader unit to restore the specified backup, providing the following parameters to the action:
- backup-id: Identifier of the backup you are attempting to restore, as saved on the S3 storage.
juju run vault/leader restore-backup backup-id=<backup-id>
The restored Vault will be unsealed and it will require to be unsealed an authorised using root token and unseal key that were in use at the time of creating the backup.
List backups
You can get a list of the identifiers of all the backups that are stored on the configured S3 storage using the list-backups
action:
juju run vault/leader list-backups
Restore Backups created in different environments
To restore a snapshot that wasn’t created using the Vault charm’s create-backup
action, you’ll need to manually upload it to the S3 storage accessible by the Vault charm where the restore-backup
action will run.
- Configure the settings for S3 storage.
- Connect to your S3 storage
- Use the same bucket configured in step 1 to store the snapshot
- Use the ID of the stored snapshot to run the restore backup action