etcd

https://etcd.io/docs/v3.8/
Admin
etcd is a strongly consistent, distributed key-value store that provides a reliable way to store...
Tokens:228,177
Snippets:1,617
Trust Score:10
Update:1 month ago
Show doc for...
Tokens:
Raw
### Put keys and get by prefix example

Source: https://etcd.io/docs/v3.8/tasks/developer/how-to-get-key-by-prefix

Shows a complete example: put three keys (web1, web2, web3) and then get all keys with the prefix 'web' using the --prefix option.

```shell
etcdctl --endpoints=$ENDPOINTS put web1 value1
etcdctl --endpoints=$ENDPOINTS put web2 value2
etcdctl --endpoints=$ENDPOINTS put web3 value3

etcdctl --endpoints=$ENDPOINTS get web --prefix
```

--------------------------------

### Set up authentication with etcdctl (role and user management)

Source: https://etcd.io/docs/v3.8/demo

Commands to configure authentication in etcd. Starts by setting the API version and endpoints, then creates a root role and user, grants permissions, and enables auth. After enabling, all client requests require authentication. Includes examples of authenticated and unauthenticated requests, showing permission denied when no user is provided.

```shell
export ETCDCTL_API=3
ENDPOINTS=localhost:2379

etcdctl --endpoints=${ENDPOINTS} role add root
etcdctl --endpoints=${ENDPOINTS} role get root

etcdctl --endpoints=${ENDPOINTS} user add root
etcdctl --endpoints=${ENDPOINTS} user grant-role root root
etcdctl --endpoints=${ENDPOINTS} user get root

etcdctl --endpoints=${ENDPOINTS} role add role0
etcdctl --endpoints=${ENDPOINTS} role grant-permission role0 readwrite foo
etcdctl --endpoints=${ENDPOINTS} user add user0
etcdctl --endpoints=${ENDPOINTS} user grant-role user0 role0

etcdctl --endpoints=${ENDPOINTS} auth enable
# now all client requests go through auth

etcdctl --endpoints=${ENDPOINTS} --user=user0:123 put foo bar
etcdctl --endpoints=${ENDPOINTS} get foo
# permission denied, user name is empty because the request does not issue an authentication request
etcdctl --endpoints=${ENDPOINTS} --user=user0:123 get foo
# user0 can read the key foo
etcdctl --endpoints=${ENDPOINTS} --user=user0:123 get foo1
```

--------------------------------

### Initial keys with revisions for past version examples

Source: https://etcd.io/docs/v3.8/dev-guide/interacting_v3

Shows the key-value pairs and their revisions used in the past version examples. The keys foo and foo1 have been modified, with revisions 2 through 5.

```text
foo = bar         # revision = 2
foo1 = bar1       # revision = 3
foo = bar_new     # revision = 4
foo1 = bar1_new   # revision = 5
```

--------------------------------

### Start etcd gateway with DNS SRV discovery

Source: https://etcd.io/docs/v3.8/op-guide/gateway

Starts the etcd gateway using DNS SRV discovery. First, the SRV records for _etcd-client._tcp.example.com are queried, then the A records for the hostnames are resolved, and finally the gateway is started with --discovery-srv=example.com. The output confirms the gateway is ready to proxy client requests.

```shell
$ dig +noall +answer SRV _etcd-client._tcp.example.com
_etcd-client._tcp.example.com. 300 IN SRV 0 0 2379 infra0.example.com.
_etcd-client._tcp.example.com. 300 IN SRV 0 0 2379 infra1.example.com.
_etcd-client._tcp.example.com. 300 IN SRV 0 0 2379 infra2.example.com.
```

```shell
$ dig +noall +answer infra0.example.com infra1.example.com infra2.example.com
infra0.example.com.  300  IN  A  10.0.1.10
infra1.example.com.  300  IN  A  10.0.1.11
infra2.example.com.  300  IN  A  10.0.1.12
```

```shell
$ etcd gateway start --discovery-srv=example.com
2016-08-16 11:21:18.867350 I | tcpproxy: ready to proxy client requests to [...]
```

--------------------------------

### Install Prometheus 2.0.0

Source: https://etcd.io/docs/v3.8/op-guide/monitoring

Downloads and extracts Prometheus version 2.0.0, then verifies the installation by running the version command.

```bash
PROMETHEUS_VERSION="2.0.0"
wget https://github.com/prometheus/prometheus/releases/download/v$PROMETHEUS_VERSION/prometheus-$PROMETHEUS_VERSION.linux-amd64.tar.gz -O /tmp/prometheus-$PROMETHEUS_VERSION.linux-amd64.tar.gz
tar -xvzf /tmp/prometheus-$PROMETHEUS_VERSION.linux-amd64.tar.gz --directory /tmp/ --strip-components=1
/tmp/prometheus -version
```

--------------------------------

### Verify etcd Installation with etcd --version

Source: https://etcd.io/docs/v3.8/install

This command verifies that the etcd binary is in the system path and displays its version. The expected output starts with 'etcd Version: ain' indicating the version number is shown.

```shell
$ etcd --version
etcd Version: ain
...
```

--------------------------------

### Start Prometheus with etcd configuration

Source: https://etcd.io/docs/v3.8/op-guide/monitoring

Starts Prometheus in the background with the specified configuration, listening on port 9090, and logs output to /tmp/test-etcd.log.

```bash
nohup /tmp/prometheus \
    -config.file /tmp/test-etcd.yaml \
    -web.listen-address ":9090" \
    -storage.local.path "test-etcd.data" >> /tmp/test-etcd.log  2>&1 &
```

--------------------------------

### Start etcd members with restored data directories

Source: https://etcd.io/docs/v3.8/op-guide/recovery

Starts three etcd members (m1, m2, m3) using the restored data directories. Each member is launched in the background with its own client and peer URLs. After starting, the restored cluster should be available and serving the keyspace from the snapshot.

```shell
$ etcd \
  --name m1 \
  --data-dir m1_data_dir.etcd \
  --listen-client-urls http://host1:2379 \
  --advertise-client-urls http://host1:2379 \
  --listen-peer-urls http://host1:2380 &
$ etcd \
  --name m2 \
  --data-dir m2_data_dir.etcd \
  --listen-client-urls http://host2:2379 \
  --advertise-client-urls http://host2:2379 \
  --listen-peer-urls http://host2:2380 &
$ etcd \
  --name m3 \
  --data-dir m3_data_dir.etcd \
  --listen-client-urls http://host3:2379 \
  --advertise-client-urls http://host3:2379 \
  --listen-peer-urls http://host3:2380 &

```

--------------------------------

### Initial keys for etcdctl read examples

Source: https://etcd.io/docs/v3.8/dev-guide/interacting_v3

Shows the initial key-value pairs used in the read examples. The keys are foo, foo1, foo2, and foo3 with corresponding values bar, bar1, bar2, and bar3.

```text
foo = bar
foo1 = bar1
foo2 = bar2
foo3 = bar3
```

--------------------------------

### Add member with etcdctl and start new etcd process

Source: https://etcd.io/docs/v3.8/op-guide/runtime-configuration

Adds a new member by name and peer URL, then starts the new etcd process with the printed environment variables and flags. The new member immediately begins catching up. Adding multiple members should be done one at a time, verifying each starts correctly. In a 1-node cluster, progress halts until the new member connects.

```shell
$ etcdctl member add infra3 --peer-urls=http://10.0.1.13:2380
added 9bf1b35fc7761a23 to cluster

ETCD_NAME="infra3"
ETCD_INITIAL_CLUSTER="infra0=http://10.0.1.10:2380,infra1=http://10.0.1.11:2380,infra2=http://10.0.1.12:2380,infra3=http://10.0.1.13:2380"
ETCD_INITIAL_CLUSTER_STATE=existing
```

```shell
$ export ETCD_NAME="infra3"
$ export ETCD_INITIAL_CLUSTER="infra0=http://10.0.1.10:2380,infra1=http://10.0.1.11:2380,infra2=http://10.0.1.12:2380,infra3=http://10.0.1.13:2380"
$ export ETCD_INITIAL_CLUSTER_STATE=existing
$ etcd --listen-client-urls http://10.0.1.13:2379 --advertise-client-urls http://10.0.1.13:2379 --listen-peer-urls http://10.0.1.13:2380 --initial-advertise-peer-urls http://10.0.1.13:2380 --data-dir %data_dir%
```

--------------------------------

### Example: etcdctl endpoint hashkv with table output

Source: https://etcd.io/docs/v3.8/tasks/operator/how-to-check-cluster-status

Example of checking KV hash with table output. Shows the hash and hash revision for each endpoint in the cluster.

```shell
etcdctl --cluster endpoint hashkv  --write-out=table

+------------------+------------+---------------+
|     ENDPOINT     |    HASH    | HASH REVISION |
+------------------+------------+---------------+
| 10.240.0.17:2379 | 3892279174 |             3 |
| 10.240.0.18:2379 | 3892279174 |             3 |
| 10.240.0.19:2379 | 3892279174 |             3 |
+------------------+------------+---------------+
```

--------------------------------

### Start etcd gateway with static endpoints

Source: https://etcd.io/docs/v3.8/op-guide/gateway

Starts the etcd gateway with static endpoints. The command lists three endpoints separated by commas, and the output confirms the gateway is ready to proxy client requests.

```shell
$ etcd gateway start --endpoints=infra0.example.com:2379,infra1.example.com:2379,infra2.example.com:2379
2016-08-16 11:21:18.867350 I | tcpproxy: ready to proxy client requests to [...]
```

--------------------------------

### Install and run etcd-dump-logs

Source: https://etcd.io/docs/v3.8/learning/persistent-storage-files

Install and run the etcd-dump-logs tool to read WAL logs. The tool prints only Entries, applies overrides to show final values, and prints uncommitted entries without HardState.commitIndex information.

```shell
% go install go.etcd.io/etcd/v3/tools/etcd-dump-logs@latest

% go run go.etcd.io/etcd/v3/tools/etcd-dump-logs --start-index=0 aname.etcd

```

--------------------------------

### Install goreman

Source: https://etcd.io/docs/v3.8/dev-guide/local_cluster

Install goreman to control Procfile-based applications. This is required to start a multi-member cluster using the provided Procfile.

```bash
$ go install github.com/mattn/goreman@latest
```

--------------------------------

### SetupLogging to enable gRPC server logs

Source: https://etcd.io/docs/v3.8/upgrades/upgrade_3_3

Shows how to set up logging with embed.Config and SetupLogging. Set Debug to true to enable gRPC server logs.

```go
import "github.com/coreos/etcd/embed"

cfg := &embed.Config{Debug: false}
cfg.SetupLogging()

```

--------------------------------

### Set up authentication with /v3/auth service

Source: https://etcd.io/docs/v3.8/dev-guide/api_grpc_gateway

Creates a root user, adds a root role, grants the role to the user, and enables authentication. Each command returns a JSON header with cluster and member IDs, revision, and raft term.

```bash
# create root user
curl -L http://localhost:2379/v3/auth/user/add \
  -X POST -d '{"name": "root", "password": "pass"}'
# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"}}

# create root role
curl -L http://localhost:2379/v3/auth/role/add \
  -X POST -d '{"name": "root"}'
# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"}}

# grant root role
curl -L http://localhost:2379/v3/auth/user/grant \
  -X POST -d '{"user": "root", "role": "root"}'
# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"}}

# enable auth
curl -L http://localhost:2379/v3/auth/enable -X POST -d '{}'
# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"}}

```

--------------------------------

### Get etcd version with etcd --version

Source: https://etcd.io/docs/v3.8/reporting_bugs

Run the etcd command with the --version flag to display the installed version.

```bash
$ etcd --version

```

--------------------------------

### Set up cluster using public discovery service

Source: https://etcd.io/docs/v3.8/tasks/operator/how-to-setup-cluster

Uses the public discovery service to bootstrap the cluster. First obtains a discovery URL with curl, then sets the DISCOVERY variable and starts etcd on each machine with the --discovery flag.

```bash
curl https://discovery.etcd.io/new?size=3
https://discovery.etcd.io/a81b5818e67a6ea83e9d4daea5ecbc92

# grab this token
TOKEN=token-01
CLUSTER_STATE=new
NAME_1=machine-1
NAME_2=machine-2
NAME_3=machine-3
HOST_1=10.240.0.17
HOST_2=10.240.0.18
HOST_3=10.240.0.19
DISCOVERY=https://discovery.etcd.io/a81b5818e67a6ea83e9d4daea5ecbc92

THIS_NAME=${NAME_1}
THIS_IP=${HOST_1}
etcd --data-dir=data.etcd --name ${THIS_NAME} \
	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
	--discovery ${DISCOVERY} \
	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}

THIS_NAME=${NAME_2}
THIS_IP=${HOST_2}
etcd --data-dir=data.etcd --name ${THIS_NAME} \
	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
	--discovery ${DISCOVERY} \
	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}

THIS_NAME=${NAME_3}
THIS_IP=${HOST_3}
etcd --data-dir=data.etcd --name ${THIS_NAME} \
	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
	--discovery ${DISCOVERY} \
	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}
```

--------------------------------

### Install cert-manager with Helm

Source: https://etcd.io/docs/v3.8/op-guide/kubernetes

Installs cert-manager into the cluster using Helm. The --set crds.enabled=true flag ensures the required CRDs are installed. Run this before creating the ClusterIssuer and Certificate resources.

```shell
$ helm upgrade --install --create-namespace --namespace cert-manager cert-manager cert-manager --repo https://charts.jetstack.io --set crds.enabled=true
```

--------------------------------

### Write benchmark commands

Source: https://etcd.io/docs/v3.8/op-guide/performance

Sample commands to benchmark write performance. Includes commands for writing to the leader with 1 connection/client and 100 connections/1000 clients, and writing to all members with 100 connections/1000 clients.

```bash
# write to leader
benchmark --endpoints=${HOST_1} --target-leader --conns=1 --clients=1 \
    put --key-size=8 --sequential-keys --total=10000 --val-size=256
benchmark --endpoints=${HOST_1} --target-leader  --conns=100 --clients=1000 \
    put --key-size=8 --sequential-keys --total=100000 --val-size=256

# write to all members
benchmark --endpoints=${HOST_1},${HOST_2},${HOST_3} --conns=100 --clients=1000 \
    put --key-size=8 --sequential-keys --total=100000 --val-size=256
```

--------------------------------

### Moved clientv3.NewFromConfigFile to clientv3.yaml.NewConfig

Source: https://etcd.io/docs/v3.8/upgrades/upgrade_3_2

Shows the before and after for the configuration file loading function, which moved from clientv3.NewFromConfigFile to clientv3yaml.NewConfig.

```go
import "github.com/coreos/etcd/clientv3"
clientv3.NewFromConfigFile

```

```go
import clientv3yaml "github.com/coreos/etcd/clientv3/yaml"
clientv3yaml.NewConfig

```

--------------------------------

### Install etcd using Homebrew

Source: https://etcd.io/docs/v3.8/install

Installs the etcd package using Homebrew on macOS. The version installed depends on the Homebrew repository, which may be outdated according to the documentation's disclaimer.

```shell
$ brew install etcd
```

--------------------------------

### Set up initial data with etcdctl put

Source: https://etcd.io/docs/v3.8/tasks/developer/how-to-transactional-write

Creates initial data for a user by putting their email and phone number into etcd keys.

```bash
etcdctl put /users/12345/email "old.address@johndoe.com"
etcdctl put /users/12345/phone "123-456-7890"
```

--------------------------------

### Get role permissions with etcdctl role get

Source: https://etcd.io/docs/v3.8/op-guide/authentication/rbac

Displays the permissions granted to the specified role.

```shell
$ etcdctl role get myrolename

```

--------------------------------

### Get a key with etcdctl get

Source: https://etcd.io/docs/v3.8/quickstart

Retrieve the value of a key using etcdctl. Run from the same terminal after setting the key.

```shell
$ etcdctl get greeting
greeting
Hello, etcd

```

--------------------------------

### Custom etcd discovery service: create size key and start members

Source: https://etcd.io/docs/v3.8/op-guide/clustering

Set up a custom etcd discovery service by creating a size key with curl, then start two etcd members using the --discovery flag. Each member must have a unique --name flag or discovery fails due to duplicated names.

```shell
$ curl -X PUT https://myetcd.local/v2/keys/discovery/6c007a14875d53d9bf0ef5a6fc0257c817f0fb83/_config/size -d value=3

```

```shell
$ etcd --name infra1 --initial-advertise-peer-urls http://10.0.1.10:2380 \
  --listen-peer-urls http://10.0.1.10:2380 \
  --listen-client-urls http://10.0.1.10:2379,http://127.0.0.1:2379 \
  --advertise-client-urls http://10.0.1.10:2379 \
  --discovery https://myetcd.local/v2/keys/discovery/6c007a14875d53d9bf0ef5a6fc0257c817f0fb83

```

```shell
$ etcd --name infra2 --initial-advertise-peer-urls http://10.0.1.12:2380 \
  --listen-peer-urls http://10.0.1.12:2380 \
  --listen-client-urls http://10.0.1.12:2379,http://127.0.0.1:2379 \
  --advertise-client-urls http://10.0.1.12:2379 \
  --discovery https://myetcd.local/v2/keys/discovery/6c007a14875d53d9bf0ef5a6fc0257c817f0fb83

```

--------------------------------

### TLS termination with gRPC proxy: start secure etcd, proxy, and test

Source: https://etcd.io/docs/v3.8/op-guide/grpc_proxy

Set up TLS termination: start a secure etcd cluster, confirm the client port serves https, start a gRPC proxy on localhost:12379 with client certificates, then test the proxy over http.

```shell
$ etcd --listen-client-urls https://localhost:2379 --advertise-client-urls https://localhost:2379 --cert-file=peer.crt --key-file=peer.key --trusted-ca-file=ca.crt --client-cert-auth

```

```shell
# fails
$ ETCDCTL_API=3 etcdctl --endpoints=http://localhost:2379 endpoint status
# works
$ ETCDCTL_API=3 etcdctl --endpoints=https://localhost:2379 --cert=client.crt --key=client.key --cacert=ca.crt endpoint status

```

```shell
$ etcd grpc-proxy start --endpoints=https://localhost:2379 --listen-addr localhost:12379 --cert client.crt --key client.key --cacert=ca.crt --insecure-skip-tls-verify &

```

```shell
$ ETCDCTL_API=3 etcdctl --endpoints=http://localhost:12379 put abc def
# OK

```

--------------------------------

### etcd --peer-cert-allowed-cn startup output

Source: https://etcd.io/docs/v3.8/op-guide/security

Command and output showing successful startup of a 3-node cluster when each member is started with --peer-cert-allowed-cn etcd.local. The output shows name resolution and client serving.

```shell
etcd --peer-cert-allowed-cn etcd.local

I | pkg/netutil: resolving m3.etcd.local:32380 to 127.0.0.1:32380
I | pkg/netutil: resolving m2.etcd.local:22380 to 127.0.0.1:22380
I | pkg/netutil: resolving m1.etcd.local:2380 to 127.0.0.1:2380
I | etcdserver: published {Name:m3 ClientURLs:[https://m3.etcd.local:32379]} to cluster 9db03f09b20de32b
I | embed: ready to serve client requests
I | etcdserver: published {Name:m1 ClientURLs:[https://m1.etcd.local:2379]} to cluster 9db03f09b20de32b
I | embed: ready to serve client requests
I | etcdserver: published {Name:m2 ClientURLs:[https://m2.etcd.local:22379]} to cluster 9db03f09b20de32b
I | embed: ready to serve client requests
I | embed: serving client requests on 127.0.0.1:32379
I | embed: serving client requests on 127.0.0.1:22379
I | embed: serving client requests on 127.0.0.1:2379

```

--------------------------------

### Removed embed.Config.SetupLogging

Source: https://etcd.io/docs/v3.8/upgrades/upgrade_3_4

Shows that `embed.Config.SetupLogging` has been removed. The example shows the old call being deleted; logging is now set up automatically.

```go
import "github.com/coreos/etcd/embed"

cfg := &embed.Config{Debug: false}
-cfg.SetupLogging()

```

--------------------------------

### Verify etcd Installed from Source

Source: https://etcd.io/docs/v3.8/install

Checks that etcd is correctly installed in the path by displaying its version. The command returns the etcd version information.

```shell
$ etcd --version
```

--------------------------------

### Read benchmark commands

Source: https://etcd.io/docs/v3.8/op-guide/performance

Sample commands to benchmark read performance. Includes single connection read requests with linearizable (--consistency=l) and serializable (--consistency=s) consistency, and many concurrent read requests with both consistency levels.

```bash
# Single connection read requests
benchmark --endpoints=${HOST_1},${HOST_2},${HOST_3} --conns=1 --clients=1 \
    range YOUR_KEY --consistency=l --total=10000
benchmark --endpoints=${HOST_1},${HOST_2},${HOST_3} --conns=1 --clients=1 \
    range YOUR_KEY --consistency=s --total=10000

# Many concurrent read requests
benchmark --endpoints=${HOST_1},${HOST_2},${HOST_3} --conns=100 --clients=1000 \
    range YOUR_KEY --consistency=l --total=100000
benchmark --endpoints=${HOST_1},${HOST_2},${HOST_3} --conns=100 --clients=1000 \
    range YOUR_KEY --consistency=s --total=100000
```

--------------------------------

### Example: etcdctl endpoint health output

Source: https://etcd.io/docs/v3.8/tasks/operator/how-to-check-cluster-status

Example of checking health of endpoints. Output shows each endpoint is healthy with the time taken to commit a proposal.

```shell
etcdctl --endpoints=$ENDPOINTS endpoint health

10.240.0.17:2379 is healthy: successfully committed proposal: took = 3.345431ms
10.240.0.19:2379 is healthy: successfully committed proposal: took = 3.767967ms
10.240.0.18:2379 is healthy: successfully committed proposal: took = 4.025451ms
```

--------------------------------

### Watch keys with /v3/watch

Source: https://etcd.io/docs/v3.8/dev-guide/api_grpc_gateway

Shows how to watch a key using the /v3/watch service. The first curl starts a watch in the background, and the second curl puts a key to trigger an event. The output shows the created watch and the resulting event.

```bash
curl -N http://localhost:2379/v3/watch \
  -X POST -d '{"create_request": {"key":"Zm9v"} }' &
# {"result":{"header":{"cluster_id":"12585971608760269493","member_id":"13847567121247652255","revision":"1","raft_term":"2"},"created":true}}

curl -L http://localhost:2379/v3/kv/put \
  -X POST -d '{"key": "Zm9v", "value": "YmFy"}' >/dev/null 2>&1
# {"result":{"header":{"cluster_id":"12585971608760269493","member_id":"13847567121247652255","revision":"2","raft_term":"2"},"events":[{"kv":{"key":"Zm9v","create_revision":"2","mod_revision":"2","version":"1","value":"YmFy"}}]}}
```

--------------------------------

### clientv3.SetLogger with grpclog.LoggerV2 (Before/After)

Source: https://etcd.io/docs/v3.8/upgrades/upgrade_3_3

Shows the change from grpclog.Logger to grpclog.LoggerV2 for clientv3.SetLogger. The old log.New does not implement the new interface.

```go
import "github.com/coreos/etcd/clientv3"
clientv3.SetLogger(log.New(os.Stderr, "grpc: ", 0))

```

```go
import "github.com/coreos/etcd/clientv3"
import "google.golang.org/grpc/grpclog"
clientv3.SetLogger(grpclog.NewLoggerV2(os.Stderr, os.Stderr, os.Stderr))

// log.New above cannot be used (not implement grpclog.LoggerV2 interface)

```

--------------------------------

### Start etcd gRPC proxy without resolver prefix

Source: https://etcd.io/docs/v3.8/op-guide/grpc_proxy

Starts a proxy without a resolver prefix. The member list API returns its own advertise-client-url as shown in the following output.

```shell
$ etcd grpc-proxy start --endpoints=localhost:2379 \
  --listen-addr=127.0.0.1:23792 \
  --advertise-client-url=127.0.0.1:23792

```
Tokens:
Raw