mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-23 23:51:08 +02:00
0660ea6fac
* Update README Let contributors know that docs will now be located in UDR * Add comments to each mdx doc Comment has been added to all mdx docs that are not partials * chore: added changelog changelog check failure * wip: removed changelog * Fix content errors * Doc spacing * Update website/content/docs/deploy/kubernetes/vso/helm.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> --------- Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
51 lines
2.0 KiB
Plaintext
51 lines
2.0 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Use built-in persistent caching - Vault Agent
|
|
description: >-
|
|
Use persistent caching with Vault Agent
|
|
---
|
|
|
|
> [!IMPORTANT]
|
|
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
|
|
|
|
# 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"
|
|
}
|
|
}
|
|
```
|