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
Investigating the use of the grpc-proxy, I get different results for the same etcdctl command when going through the proxy vs. going direct to the etcd cluster- specifically, the --keys-only flag is ignored.
I'm running the grpc proxy with the following command:
pwoodman@mk8s01-dca1:~/etcd/etcd-v3.2.6-linux-amd64$ ./etcd grpc-proxy start --endpoints=http://m3-kv02-dca1:2379
2017-08-31 22:21:17.272813 I | etcdmain: listening for grpc-proxy client requests on 127.0.0.1:23790
2017-08-31 22:21:17.289372 E | etcdmain: forgot to set Type=notify in systemd service file?
I'd expect the following two commands to return the same result, but they don't:
Investigating the use of the grpc-proxy, I get different results for the same etcdctl command when going through the proxy vs. going direct to the etcd cluster- specifically, the --keys-only flag is ignored.
I'm running the grpc proxy with the following command:
I'd expect the following two commands to return the same result, but they don't:
The text was updated successfully, but these errors were encountered: