<p>All the secrets used by our application are stored in Vault. During deployment, we utilize an internal tool to retrieve secrets from Vault and load them onto the pods. Now, we have a secret which gets updated every month and it requires a restart or deployment. Is there a solution available that automates the process of updating the secret on the pod whenever it is modified on Vault? FYI - our secrets are loaded as files on the pods.</p>
<p>I checked online and I see two options:</p>
<p>1 - Vault agent used as side car container
2 - Vault operator (something new)</p>

Sandeep
<p>Sidecar would fit in nicely.</p>
<p>That Hashicorp <a href="https://www.hashicorp.com/blog/vault-secrets-operator-a-new-method-for-kubernetes-integration" rel="nofollow noreferrer">Vault Secrets Operator</a> could do as well, I guess -- I didn't know about it, TBH.</p>
<p>You could attach secrets as <a href="https://developer.hashicorp.com/vault/tutorials/kubernetes/kubernetes-secret-store-driver" rel="nofollow noreferrer">CSI Volumes</a></p>
<p>Inject them using Hashicorp <a href="https://developer.hashicorp.com/vault/tutorials/kubernetes/kubernetes-sidecar" rel="nofollow noreferrer">Vault Agent</a></p>
<p>And we could mention: the <a href="https://external-secrets.io/" rel="nofollow noreferrer">External Secrets Operator</a>, which can integrate with other vaults (eg: aws, a remote kubernetes cluster API, ...)</p>
