Thomas Jungblut
Thomas Jungblut
/test e2e-aws-etcd-recovery
/test e2e-aws-etcd-recovery
/test e2e-aws-etcd-recovery
/test e2e-aws-etcd-recovery
/test e2e-aws-etcd-recovery
/test e2e-aws-etcd-recovery
/retest-required
Thanks for the suggestion @ahrtr. I'm just briefly browsing through the code right now, but this still would require a clientTLSInfo: https://github.com/etcd-io/etcd/blob/main/server/embed/etcd.go#L828-L842 We need all endpoints with https, metrics need...
Sure. ``` $ etcd --cert-file=etcd-serving-fedora.crt \ --key-file=etcd-serving-fedora.key \ --trusted-ca-file=ca.crt \ --client-cert-auth=true \ --listen-client-urls=https://localhost:2379 \ --advertise-client-urls=https://localhost:2379 \ --listen-metrics-urls=https://localhost:1337 ``` curling just the endpoint yields: ``` $ curl https://localhost:1337/health curl: (60) SSL...
Yes @serathius I understood what @ahrtr meant, we can't have unprotected (as in plain HTTP) endpoints running.