ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #vault
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?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?