could somebody please explain why, when configuring a secure etcd cluster, we need to provide the client private key? Cf --key-file here: https://coreos.com/etcd/docs/latest/op-guide/security.html
I've never seen this in HTTPS 2 way ssl, for me, this key should never go out of the server.
Thanks for your help.
Further reading has clarified things for me, especially the example 3: https://coreos.com/etcd/docs/latest/op-guide/security.html
So --key-file and --peer-key-file are both the SERVER keys used by clients when ETCD acts as server, they may be different if we have two different keypairs for peers and clients.
It's clear now, the client's private key remains private :) So everything is OK.