Allow talking to secure etcd (authentication through client certs)

[dhawal55]

Fixes issue #244
We will need more work to support secure etcd for self-hosted etcd

[peebs]

ok to test

[dhawal55]

Can someone look at my pull requests? Really simple ones

[aaronlevy]

Hi @dhawal55, sorry for the delay.

We are planning on migrating to self-hosted etcd cluster as the default very soon (#31) -- so the way each etcd node is launched (and where it sources TLS assets) will change almost completely. This is definitely something we need, but if we try to implement this functionality now, it will pretty much have to be thrown out / re-done differently very soon.

[dhawal55]

@aaronlevy The experimental-self-hosted-etcd currently doesn't support TLS, nor does the etcd-operator. I'm okay closing this PR if issue #31 includes TLS support for etcd.

[aaronlevy]

#31 doesn't explicitly cover handling TLS support (and the initial implementation likely won't). I think we should keep #244 open to track this need.

[ghost]

Can one of the admins verify this patch?

[ghost]

Can one of the admins verify this patch?

[aaronlevy]

This has been added in #433