tokers commented on issue #90: URL: https://github.com/apache/apisix-docker/issues/90#issuecomment-737624844
> @gxthrj > I am sure that I can communicate with 10.1.7.51 2379 in the same container > > This is the startup parameter of my etcd cluster. I wonder if it is related to the "--enable-v2=true" parameter. > > ``` > root 11701 2.4 3.1 10888476 322624 ? Ssl 11月22 321:14 /usr/local/bin/etcd --listen-client-urls=https://0.0.0.0:2379 \ > --initial-advertise-peer-urls=https://10.1.7.51:2380 --key-file=/etc/kubernetes/ssl/kube-etcd-10-1-7-51-key.pem \ > --peer-key-file=/etc/kubernetes/ssl/kube-etcd-10-1-7-51-key.pem --peer-client-cert-auth=true \ > --initial-cluster-token=etcd-cluster-1 --name=etcd-master1 --cert-file=/etc/kubernetes/ssl/kube-etcd-10-1-7-51.pem \ > --advertise-client-urls=https://10.1.7.51:2379,https://10.1.7.51:4001 --enable-v2=true --data-dir=/var/lib/rancher/etcd/ \ > --listen-peer-urls=https://0.0.0.0:2380 --initial-cluster-state=new --peer-trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem \ > --peer-cert-file=/etc/kubernetes/ssl/kube-etcd-10-1-7-51.pem --initial-cluster=etcd-master1=https://10.1.7.51:2380,etcd-worker1=https://10.1.7.52:2380,etcd-worker2=https://10.1.7.53:2380 \ > --trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --client-cert-auth=true --election-timeout=5000 --heartbeat-interval=500 > ``` The option `--client-cert-auth=true` is used in your etcd server, which forces the clients offer their own certificate to meet the mTLS, which is not supported by APISIX. If the mLTS is not required necessarily, just remove it. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
