You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The root cause of the recent problem fixed in #10366 is that etcd uses a certificate to itself. If etcd uses non TLS unix domain socket for the internal RPCs from gateway, the possibility of such a problem can be much more reduced.
(socketpair(2) is the ideal solution because it is completely invisible from outside but grpc-go seems to be not supporting creating connection from fd: grpc/grpc#6610)
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.
The root cause of the recent problem fixed in #10366 is that etcd uses a certificate to itself. If etcd uses non TLS unix domain socket for the internal RPCs from gateway, the possibility of such a problem can be much more reduced.
cc @hexfusion @gyuho @xiang90 @jpbetz
(
socketpair(2)
is the ideal solution because it is completely invisible from outside but grpc-go seems to be not supporting creating connection from fd: grpc/grpc#6610)The text was updated successfully, but these errors were encountered: