mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-23 15:41:07 +02:00
fd00bbfd1b
* Update Vault Agent docs * Update left-hand nav * tweak caching titles * tweak deprecation/warning * tweaks to match proxy updates
48 lines
1.5 KiB
Plaintext
48 lines
1.5 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Use built-in persistent caching - Vault Agent
|
|
description: >-
|
|
Use persistent caching with Vault Agent
|
|
---
|
|
|
|
# Use built-in persistent caching
|
|
|
|
Vault Agent can restore tokens and leases from a persistent cache file created
|
|
by a previous Vault Agent process. The persistent cache is a BoltDB file that
|
|
includes tuples encrypted by a generated encryption key. The encrypted tuples
|
|
include the Vault token used to retrieve secrets, leases for tokens/secrets, and
|
|
secret values.
|
|
|
|
-> **Note:** Vault Agent Persistent Caching will only restore _leased_
|
|
secrets. Secrets that are not renewable, such as KV v2, will not be persisted.
|
|
|
|
In order to use Vault Agent persistent cache, auto-auth must be used. If the
|
|
auto-auth token has expired by the time the cache is restored, the cache will
|
|
be invalidated and secrets will need to be re-fetched from Vault.
|
|
|
|
If Vault Agent templating is enabled alongside of the persistent cache, Vault
|
|
Agent will automatically route templating requests through the cache. This
|
|
ensures template requests are cached and restored properly.
|
|
|
|
-> **Note** Vault Agent persistent cache is currently supported only in a
|
|
Kubernetes environment.
|
|
|
|
## Vault agent persistent cache types
|
|
|
|
Please see the sidebar for available types and their usage/configuration.
|
|
|
|
## Persistent cache example configuration
|
|
|
|
Here is an example of a persistent cache configuration.
|
|
|
|
```hcl
|
|
# Other Vault agent configuration blocks
|
|
# ...
|
|
|
|
cache {
|
|
persist "kubernetes" {
|
|
path = "/vault/agent-cache"
|
|
}
|
|
}
|
|
```
|