Releasing HashiCorp Vault Helm Chart 0.2.0
The Vault team is happy to announce the release of an updated version of the Helm Chart for Vault. The Vault Helm Chart greatly reduces the complexity of running Vault on Kubernetes, and allows for Vault clusters to be up and running in just minutes. If you would like to learn more please see our initial release announcement.
» What's New
Here are a few highlights from the Vault Helm Chart 0.2.0 release. These mostly consist of several requested features, many feature improvements, and bug fixes.
- Added Load Balancer & Ingress support
- Removed root requirements, now runs as Vault user
- Improvements (configurable ports, Read Only Root FS, annotations, etc)
Please see the changelog for a complete listing. We also wanted to thank the community for the great feedback, as it helps drive improvements to the Helm Chart, and also highlight areas for improvement.
» Next Steps
The updated 0.2.0 Helm chart is available now on GitHub. To learn more, please see the Helm Chart documentation, or the documentation on Running Vault on Kubernetes. Also, if you enjoy playing around with this type of stuff, maybe you’d be interested in working at Hashicorp too since we're hiring!
Sign up for the latest HashiCorp news
More blog posts like this one

Secure AI workloads on Google Cloud with HashiCorp Vault
Learn how HashiCorp Vault integrates with Google Cloud to manage dynamic credentials and enforce access controls for AI services like Vertex AI and AutoML.

HCP Vault Radar agent: Local secret scanning at enterprise scale
The Vault Radar agent enables hybrid secret scanning across source code and collaboration tools within your environment, delivering deep visibility and risk reduction without sensitive data leaving your network.

Harvest now, decrypt later: Why today’s encrypted data isn’t safe forever
Harvest now, decrypt later attacks involve collecting encrypted data today to break it with quantum computers tomorrow — posing a silent, long-term threat.