vault-helm

Deploy and configure HashiCorp Vault on Kubernetes via Helm with HA Raft storage.

4|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill vault-helm-aidas-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vault-helm
Source: https://github.com/Aidas-dev/k8s-agent-skills/tree/main/skills/vault-helm
Command: npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill vault-helm-aidas-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying HashiCorp Vault on Kubernetes involves intricate Helm chart values, HA Raft consensus setup, and manual post-install steps like initialization, unsealing, and Raft peer joining that are easy to get wrong. ## Core Features & Use Cases - Flux HelmRelease Configuration: Provides a complete HelmRelease manifest with HA+Raft mode, telemetry, storage classes, and UI settings for chart 0.33.0. - Post-Deploy Runbook: Step-by-step commands for operator init, unsealing all pods with key shares, Raft join for standby nodes, and cluster verification. - HA Config Reference: Documents raw HCL stanzas for listeners, Raft storage, and Kubernetes service registration, plus common mistakes like injector/ESO conflicts and unseal key loss. - Use Case: A platform engineer needs a highly available Vault cluster on Kubernetes with Prometheus metrics and Gateway-terminated TLS; this Skill supplies the exact Helm values and the ordered init/unseal/join procedure. ## Quick Start Deploy Vault on my Kubernetes cluster in HA mode with Raft storage using the Helm chart and walk me through initialization and unsealing.

Frequently Asked Questions about vault-helm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy HashiCorp Vault on Kubernetes with Helm?▼

Create a Flux HelmRelease referencing the hashicorp/vault chart version 0.33.0 with server.ha.enabled and server.ha.raft.enabled set to true. Provide raw HCL in server.ha.raft.config for the listener, Raft storage path, and Kubernetes service registration.

How do I unseal Vault pods after Helm deployment?▼

Run vault operator init on vault-0 to generate unseal keys and a root token, then execute vault operator unseal with 3 of 5 key shares on every pod. Standby pods must also run vault operator raft join against vault-0 to become cluster members.

Should I use Vault or OpenBao for self-hosted secrets management?▼

OpenBao is a drop-in-compatible Vault fork that includes namespaces and static key auto-unseal in the open-source build, features Vault gates behind Enterprise. The hashicorp/vault Helm chart values mostly apply to OpenBao with an image swap, though replication is not yet available.

Does the Vault Helm chart work with External Secrets Operator?▼

Yes, but you should disable the Vault agent injector by setting injector.enabled to false when using External Secrets Operator. Both components mutate pods and can conflict if left enabled simultaneously.

Why is my Vault cluster not forming after deployment?▼

The most common cause is skipping the Raft join step for vault-1 and vault-2, leaving them as non-member standbys. Also verify at least a quorum of pods (2 of 3) are unsealed and check cluster state with vault operator raft list-peers.

What are the limitations of Vault OSS on Kubernetes?▼

Vault OSS lacks namespaces, disaster recovery replication, Sentinel policies, SAML auth, and OTLP traces, which are Enterprise-only features. It supports Raft HA, Kubernetes auth, KV v2, ACL policies, and Prometheus metrics.