*: make default etcd version to 3.2.10

[hongchaodeng]

fix #1396

Blockers:

• etcd 3.2: seed member panic, second member is still being added #1614

[hongchaodeng]

Has TLS issue with 3.2.9:

2017-10-31 18:19:27.991428 I | etcdmain: rejected connection from "10.2.3.149:55104" (tls: "10.2.3.149" does not match any of DNSNames ["*.example-vault-etcd.hongchao-test.svc" "*.example-vault-etcd.hongchao-test.svc.cluster.local"])
...

2017-10-31 18:19:41.334025 W | rafthttp: health check for peer b1b48150f4da7b66 could not connect: dial tcp 10.2.3.149:2380: i/o timeout

[hongchaodeng]

etcd upstream issues ref:

• etcd v3.2.5 tls broken or a breaking change is introduced etcd-io/etcd#8534
• Peer TLS SAN check couldn't reason about non-FQDN endpoints etcd-io/etcd#8797

We have to work around the issue right now by providing FQDN in peer certs.

[hongchaodeng]

Even after adding cluster domain into peer SAN, etcd server still occasionally rejected connection with error:

etcdmain: rejected connection from "10.60.6.133:60520" (
tls: "10.60.6.133" does not match any of DNSNames
["*.tls-test-5577006791947779410.e2e-etcd-operator-e2eslow-pr-837.svc" 
 "*.tls-test-5577006791947779410.e2e-etcd-operator-e2eslow-pr-837.svc.cluster.local"] 
(lookup 133.6.60.10.in-addr.arpa. on 10.63.240.10:53: no such host))

Still needs more investigation.

[hongchaodeng]

Also high chance for this error:

2017-11-01 16:31:59.792577 W | etcdserver: could not get cluster response from https://example-0000.example.default.svc:2380:
Get https://example-0000.example.default.svc:2380/members: EOF
2017-11-01 16:31:59.798122 C | etcdmain: cannot fetch cluster info from peer urls:
could not retrieve cluster information from the given urls

[hongchaodeng]

All tests fixed

[fanminshi]

what if version is 3.0.x? Will this code find the right image?

maybe we should also pass in the base image as a param.

[fanminshi]

lgtm