HashiCorp Vault and Kubernetes are a common pairing in a modern DevOps stack. Here is how they fit together and a practical way to wire them up.
Where HashiCorp Vault fits
Vault stores and controls access to secrets, issues short-lived dynamic credentials for databases and clouds, and provides encryption-as-a-service - all behind identity-based policies and a full audit log.
vault secrets enable -path=secret kv-v2
vault kv put secret/app/db password=s3cr3t
cat <<EOF | vault policy write app -
path "secret/data/app/*" { capabilities = ["read"] }
EOFWhere Kubernetes fits
Kubernetes is a container orchestrator: you declare the desired state of your workloads in YAML and controllers continuously reconcile the cluster toward it, handling scheduling, scaling, healing and networking.
apiVersion: apps/v1
kind: Deployment
metadata: { name: web }
spec:
replicas: 3
selector: { matchLabels: { app: web } }
template:
metadata: { labels: { app: web } }
spec:
containers:
- name: web
image: ghcr.io/acme/web:1.0
ports: [{ containerPort: 3000 }]
resources:
requests: { cpu: 100m, memory: 128Mi }
limits: { cpu: 500m, memory: 256Mi }
readinessProbe:
httpGet: { path: /healthz, port: 3000 }
---
apiVersion: v1
kind: Service
metadata: { name: web }
spec:
selector: { app: web }
ports: [{ port: 80, targetPort: 3000 }]Making them work together
- Use auth methods (Kubernetes, OIDC, AppRole) with least-privilege policies
- Prefer dynamic secrets with short TTLs over static ones
- Set requests/limits and use the HorizontalPodAutoscaler for elastic workloads
- Separate config (ConfigMap) from secrets and mount them, don't bake them in
Want this pairing set up properly, with docs and handover? That is exactly the kind of work CodeWizard's embedded senior engineers do - and both HashiCorp Vault and Kubernetes have active community groups you can join for free.