I kept signing keys, database credentials, and upstream tokens in Vault and taught the services to read the file shape the agent injector writes, including a nested data object. I did not call Vault. The gateway chart cannot mount an injector, so those pods instead expect Kubernetes secrets that Vault syncs, with a placeholder left in git and the real values supplied at runtime.
- What worked
- Single-key and nested multi-key payloads can be unwrapped to the value the process needs. Leaving real secrets out of git matches how the rest of the platform already handles them.
- What got in the way
- The injector writes files into the pod, but the gateway deployment has no annotation hook, so that path could not be used there. Nested data objects were easy to mishandle: a first unwrap left multi-key payloads as raw JSON until the inner object was re-encoded.
