[wip] etcd: Connection options (socket file, ipv6)#343
[wip] etcd: Connection options (socket file, ipv6)#343aequitas wants to merge 2 commits intopurpleidea:masterfrom
Conversation
|
|
Awaiting: grpc/grpc-go#1741 (comment) Grpc seems to be hardcoded to "tcp". Functional wise unix domain sockets work well. I still have to run more extensive tests, but deployment of |
|
In other news, functional wise unix domain sockets work even with the grpc warnings. |
|
Raised issue at etcd: etcd-io/etcd#9340 |
245e927 to
7b178e9
Compare
|
This PR currently included integrationtest commit as it is a prerequisite for the domain socket test. |
7b178e9 to
bed6eae
Compare
|
Tests seem to prove this is functional even with the gprc error. |
35f0a3c to
71ea635
Compare
71ea635 to
75f323e
Compare
|
Removed that commit again as it did not build a proper binary, probably due to changes in how etcd handles dependencies now since v3.3.1. |
75f323e to
d74099a
Compare
f19437c to
5754903
Compare
- Allow unix domain socket to be used as client url - Using ::1 as clienturl should not create default local ipv4 listener - Add shell testsuite that runs using unix domain sockets
5754903 to
2113d0c
Compare
Changes:
Todos:
Currently this allows a mgmt instance to be started with no TCP ports opened, eg using:
And run
mgmt deployutilising the socket connection (deploy needs to be run from prefix directory).Only problems I still need to solve is related to gprc:
I have been debugging for a while now and still unsure why this happens.