Description
Hello @wealdtech ,
First of all, thank you for your jobs on ETH2 validation components.
I'm Cloud Architect working for Stake Capital and I'm building an ETH2 validation infrastructure to provide a large range of validators.
The technical stack is build on top of EKS (Kubernetes managed service on AWS) for Dirk and Vouch.
Historically, we are using Hashicorp Vault (https://www.vaultproject.io/) for secret management and we want to use it as wallet storage for this infra.
We are using Vault as Certificate Authority too to manage certificate of Dirk and Vouch services
So, I've fork your S3 wallet store librairy and i've adapted it to work with the KVv2 of vault storage:
https://github.com/bliiitz/go-eth2-wallet-store-vault (tests inside hasn't been updated)
For Vault authentication, I've implemented 2 ways:
- Provide directly a vault token (for test localy)
- Authentication with Kubernetes service account (for production)
After that, I've fork and update Dirk to handle this new lib:
https://github.com/bliiitz/dirk/blob/master/core/stores.go#L82
And now for wallet management, I've fork ethdo to add vault storage and be allowed to manage wallets with a pod spawned in the Kubernetes cluster.
What do you think about to merge this forks on your repos ?
Can we have a discussion about this ? (i'm not a golang expert so i prefer discuss about your development standard)
Thanks you !