ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #vault
Move beyond static passwords by using Vault's database secrets engine to generate unique, short-lived credentials that expire automatically.
Vault’s AppRole auth method gives microservices short‑lived tokens without storing long‑term credentials. This guide walks through creating a role, generating and rotating Secret IDs, verifying token policies, and lists key trade‑offs and a production checklist.
Learn how to use HashiCorp Vault to generate short-lived AWS IAM credentials, reducing the risk of long-lived credentials being exposed.
Nomad’s template stanza lets you inject dynamic configuration from Consul KV or Vault into your tasks, automatically restarting or signaling the process when values change. This guide shows how to set up a template, explains change modes, and covers common pitfalls and verification steps.
Vault Kubernetes Auth Configuration The Kubernetes auth method in Vault (v1.12+) relies on the vault.hashicorp.com/role annotation on a pod's service account to bind the identity to a specific Vault role. In local development environments, this annotation is often present by default or injected via local tooling, ensuring seamless secret retrieval. In produc
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
Vault Namespace Token Policy Inheritance The goal is to clarify whether a token created in a parent namespace with an attached policy automatically grants the same policy permissions when the token is used to access secrets in a child namespace. Current documentation does not state if the policy is inherited, overridden, or requires explicit binding in each
The goal is to enumerate every key under a large KV v2 path using the /v1/secret/metadata/?list=true endpoint. The current implementation returns a plain keys array with no continuation token, so the caller must rely on prefix filtering to simulate pagination. Performance degrades noticeably with more than ~1,000 entries, and there is no documented cap on th
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
consul
nomad