Applications and operators need credentials, but copying passwords and tokens into many separate configurations makes access and rotation difficult to manage. HashiCorp Vault provides a service for storing or generating supported secrets and controlling who can retrieve them. Teams can centralize policies and audit secret access while selecting a delivery method for their workloads. Operating Vault itself requires a durable storage design, initialization and recovery procedures; installing a chart does not complete those responsibilities.
Current guidance
HashiCorp documents a current Helm chart for Vault, while server operations and application secret delivery remain separate responsibilities.
The chart’s default standalone mode uses one Vault server with file storage, which its documentation explicitly marks as unsuitable for production. Choose a supported storage and availability model, then plan initialization, unseal/recovery, authentication, backups and upgrades. A chart installation is not a complete production operating procedure.
Test recovery in a separate environment and review who can access administrative keys and tokens. For workloads, compare injection, CSI or synchronization approaches according to rotation and access requirements. Never confuse the historical CoreOS operator with a current delivery integration.
Historical upstream link check · 2026-10-09
The recorded upstream address redirects to https://developer.hashicorp.com/vault/docs and returned HTTP 200 on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, or certificates. Vault provides a unified interface to any secret while providing tight access control and recording a detailed audit log.
A modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where Vault steps in.
The key features of Vault are:
- Secure Secret Storage: Arbitrary key/value secrets can be stored in Vault. Vault encrypts these secrets prior to writing them to persistent storage, so gaining access to the raw storage isn’t enough to access your secrets. Vault can write to disk, Consul, and more.
- Dynamic Secrets: Vault can generate secrets on-demand for some systems, such as AWS or SQL databases. For example, when an application needs to access an S3 bucket, it asks Vault for credentials, and Vault will generate an AWS keypair with valid permissions on demand. After creating these dynamic secrets, Vault will also automatically revoke them after the lease is up.
- Data Encryption: Vault can encrypt and decrypt data without storing it. This allows security teams to define encryption parameters and developers to store encrypted data in a location such as SQL without having to design their own encryption methods.
- Leasing and Renewal: All secrets in Vault have a lease associated with them. At the end of the lease, Vault will automatically revoke that secret. Clients are able to renew leases via built-in renew APIs.
- Revocation: Vault has built-in support for secret revocation. Vault can revoke not only single secrets, but a tree of secrets, for example, all secrets read by a specific user, or all secrets of a particular type. Revocation assists in key rolling as well as locking down systems in the case of an intrusion.
Sources & further reading
Spotted something that needs another look?
Help improve this page →