From d7efc88b7d44691d746228f2a6e42c72ad12fccd Mon Sep 17 00:00:00 2001 From: Ben McCann Date: Mon, 1 Jun 2015 20:10:45 -0700 Subject: [PATCH] Document how a secrets server like Vault or Keywhiz might fit into Kubernetes --- docs/design/secrets.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/design/secrets.md b/docs/design/secrets.md index 5f8cb50184570..e96b0d89e0e1b 100644 --- a/docs/design/secrets.md +++ b/docs/design/secrets.md @@ -148,7 +148,8 @@ have different preferences for the central store of secret data. Some possibili 1. An etcd collection alongside the storage for other API resources 2. A collocated [HSM](http://en.wikipedia.org/wiki/Hardware_security_module) -3. An external datastore such as an external etcd, RDBMS, etc. +3. A secrets server like [Vault](https://www.vaultproject.io/) or [Keywhiz](https://square.github.io/keywhiz/) +4. An external datastore such as an external etcd, RDBMS, etc. #### Size limit for secrets