High-availability HashiCorp Vault deployment on Kubernetes uses a StatefulSet with three pods: one active and two standby replicas for automatic failover. The architecture spans vault-system and vault namespaces, with Ingress routing external traffic to Vault Service endpoints, while PersistentVolumeClaims ensure durable storage for secrets. RBAC controls via ServiceAccount, ClusterRole, and ClusterRoleBinding enforce least-privilege access, while NetworkPolicy isolates vault namespace traffic and HPA enables autoscaling. Fork this diagram on Diagrams.so to customize namespace topology, adjust replica counts, or integrate with your existing Kubernetes monitoring stack. The StatefulSet pattern with dedicated PersistentVolumes guarantees each Vault pod maintains state across restarts, critical for unsealing operations and HA consensus.