Does Vault Secret Operator automatically do client-side caching for KVv1 and KVv2?

HashiCorp Cloud Platform (HCP) HCP Vault Secrets
,
1

Hi experts,
I am using the Vault Secret Operator.
I am wondering whether VSO also does automatically client-side caching for KVv1 and KVv2 secrets to minimize requests made to Vault and provide resilient connections for clients, similar to Vault Proxy?

2

VSO takes a secret from Vault and creates a Kubernetes Secret. In terms of minimizing requests to Vault - yes - in that your Kubernetes workloads are reading the Kubernetes Secret, not making a call to Vault for the secret.

VSO is checking for updates to secrets in Vault, and updating the Kubernetes Secret when a change is detected. If you are using Vault Enterprise, you can optionally use instant updates, which relies on Vault Enterprise’s event notifications.

This tutorial may be helpful:

3

Thanks for the quick response.

We are using VSO now, but just wondering if the Vault server is down, does VSO have some cached values?

Also we are using Vault Enterprise.
I am wondering which way is better? VSO checking vault server for every minutes or instant updates.
Which way would introduce more stress to VSO or Vault server?