coreos / vault-operator

Run and manage Vault on Kubernetes simply and securely
https://coreos.com/blog/introducing-vault-operator-project
Apache License 2.0
758 stars 110 forks source link

Auto initialize vault #307

Open raoofm opened 6 years ago

raoofm commented 6 years ago

Vault should be auto initialized and the keys should be sent to aws kms. Either kube2iam be used to pass the aws credentials or accessKey/SecretKey pair can be used too.

Initial check should be made if vault was initialized before. If yes, then #308 or continue with init.

thrawn997 commented 6 years ago

Wouldn't it be better to just store the unseal keys as a secret? Seems less cloud specific to do it that way.

philips commented 6 years ago

I would like to have someone build a design doc on how we can do this based on kubelet identity and Kubernetes secrets instead of using kube2iam. This will ensure good security and generic application across cloud providers.

thrawn997 commented 6 years ago

I'd be new to doing that, but can learn if you can point me to the existing document (if one exists) for using kube2iam.

raoofm commented 6 years ago

It is new to me as well, I'm fine to contribute to the design(sample?).

I suggested kms because of the below reasons

deedubs commented 6 years ago

@philips do you have a rough outline the community could fill out?

Quickly thinking we could:

  1. kubelets generate PGP keys a. store private key locally(?) b. store public key as secret
  2. vault operator divides key into N parts encrypts it with the kubelet private keys and writes them to secrets
  3. vault operator deploys new "unlocker" daemonset to kubelets a. unlocker watches vault state, if its locked they... b. decrypt their key and sends it to unlock
  4. when a new node comes online we follow https://www.vaultproject.io/guides/operations/rekeying-and-rotating.html and rotate the stored keys

Please just consider this a conversation starter... 😃

thrawn997 commented 6 years ago

Assuming Vault is in an HA state, would it be possible to store as kubernetes secrets as long as you have secrets encrypted? Secrets can be encrypted with Vault now: https://github.com/oracle/kubernetes-vault-kms-plugin/blob/master/README.md

deedubs commented 6 years ago

That would make the initial bootstrapping step different from the 'normal case' which is dangerous in my experience.

thrawn997 commented 6 years ago

Wouldn't the bootstrap process stay the same? It would just reinforce that an org using a KMS should be encrypting their kubernetes secrets.

deedubs commented 6 years ago

It would stay the same in that it would still be manual