Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Vault as statefulset #323

Open
thereallukl opened this issue Jun 6, 2018 · 2 comments
Open

Vault as statefulset #323

thereallukl opened this issue Jun 6, 2018 · 2 comments

Comments

@thereallukl
Copy link

I'm working on automated deployment of vault with operator. What I noticed is that the operator is setting instances as deployment. It makes unsealing particular instances a bit troublesome (I need to check k8s API for IP of particular instance and then connect to it. I believe migrating to statefulset with known DNS names for each instance would make automated unsealing much easier.
What do you think about?

Thanks.

@thereallukl
Copy link
Author

Small update for automated unsealing. I had to implement unsealing quickly, so I prototyped a solution with sidecar container[1]. It assumes IAM roles [2] are set for nodes running vault cluster.

[1] https://github.com/coreos/vault-operator/compare/master...lleszczu:add_unsealer?expand=1
[2] https://github.com/jetstack/vault-unsealer/pull/9/files

@raoofm
Copy link

raoofm commented Jun 21, 2018

@hasbro17 @philips vault-unsealer seems like a good option for #307 and #308

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants