Alex Zhang 5191374545 feat: support TLS connection with etcd. (#2548) ... Support the TLS connection when communicating with etcd cluster. We added a configuration item to custom the certificate verification. Whether to setup TLS connection or not depends on the endpoints' scheme, for instance, when endpoints are: ``` etcd: host: - "https://127.0.0.1:2379" - "https://127.0.0.1:3379" ``` APISIX will originate TLS connection automatically, and the Server Name Indication extention will be set by the endpoint host (`127.0.0.1` in above case). Note by default APISIX will verify the certificate, close the verification in configuration explicitly if you want to bypass it. ``` etcd: tls: verfiy: false ```		2020-11-03 13:53:39 +08:00
..
cert	feature: support multiple certificates(RSA and ECC) for single domain (#2089)	2020-08-24 09:23:06 +08:00
apisix.yaml	bugfix: skipped to init etcd if use local file as config center. (#737)	2019-11-02 07:59:59 +08:00
config-default.yaml	feat: support TLS connection with etcd. (#2548)	2020-11-03 13:53:39 +08:00
config.yaml	bugfix(CLI): if the user used default token and allow any IP to access Admin API, will show a WARNING message.(#2244)	2020-09-22 16:09:35 +08:00
debug.yaml	license: add ASF header. (#743)	2019-10-31 09:27:28 +08:00
mime.types	init version.	2019-04-10 11:08:25 +08:00