Vault-k8s

First-class integrations between Vault and Kubernetes.

  • Infrastructure
  • Security
  • Tools & Utilities
First-class integrations between Vault and Kubernetes.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

67/100 Good

Maintained
84last commit 25 days ago
Popular
59842 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI, tests, OpenSSF Scorecard 6.3/10

Based on 4 of 5 factors.

GitHub stars
842
Open issues
128
Last commit
2026-10-27
Latest release
v1.7.7
License
MPL-2.0
Activity
rising

Checked 16 days ago - source: GitHub (hashicorp/vault-k8s)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Point Vault Agent at its config file If you're using Vault Agent, pass your config file path with -config (for example /path/to/file.hcl, where HCL is HashiCorp's config language). That file holds the settings needed to reach Vault and fetch secrets, so if the path is wrong the app may start but fail to get credentials. source
  • Confirm secret engines are mounted After setup, run `vault secrets list` to see the mounted secret engines (storage areas for secrets), such as private/ and shared/ for KV (a simple key-value store). If a path your app expects is missing, secret lookups and writes will fail. source
  • Set max versions if you need rollback Use `vault kv metadata put` with `-max-versions` on a KV path if you need to keep a specific number of older secret versions. Without this setting, you rely on Vault's default behavior, and older values may not be available for rollback. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should Kubernetes workloads fetch Vault secrets instead of syncing them into Kubernetes secrets?

Avoid syncing Vault secrets to Kubernetes secrets. Use a Vault agent sidecar and a token file so the app pulls the secrets from Vault.

What Vault Agent configuration mistake can cause an app to start but fail to retrieve credentials?

Pass the correct config file path with -config. If the path is wrong, the app may start but fail to get credentials.

How can I confirm that the secret paths my application expects are available in Vault?

Run vault secrets list after setup to confirm the mounted secret engines. If a path your app expects is missing, secret lookups and writes will fail.

How do I keep older KV secret versions for rollback?

Set max versions with vault kv metadata put and -max-versions on the KV path. Without this setting, older values may not be available for rollback.

Should Vault be run on Kubernetes or a dedicated VM for production?

One user would install Vault on a dedicated VM and operate it with maximum security. Development mode is easy to run, but production needs to be locked down.

Answers sourced from developer.hashicorp.com, developer.hashicorp.com, developer.hashicorp.com, www.reddit.com, www.redditmedia.com

Community

Collected 48 days ago - public community threads