Skip to main content

​
etcd Connections

TablePro connects to etcd v3 over the HTTP/JSON gRPC-gateway (it never speaks raw gRPC). On connect it probes the /v3/, /v3beta/, and /v3alpha/ gateway prefixes in order, so etcd 3.2 through current releases work without configuration. Browse keys grouped by prefix, edit values in the grid, and run etcdctl-style commands in the editor.

​
Quick Setup

Click New Connection, select etcd, enter host (default localhost) and port (default 2379), and connect. The plugin auto-installs, or use Settings > Plugins > Browse > etcd Driver.

​
Connection Settings

With a username set, TablePro exchanges the credentials for a gateway token via the gateway’s auth/authenticate endpoint and retries once with a fresh token when a request returns 401.

​
Advanced Fields

For self-signed certificates, pick Required (skip verify) or set the CA Certificate path.

​
Connection URL

Both schemes are accepted when importing a URL. The scheme alone does not switch TLS on; set TLS Mode in the Advanced fields.

​
Browsing Keys

The sidebar groups keys by their first path segment under the Key Prefix Root; keys without a segment appear under (root). The grid shows one row per key with the columns Key, Value, Version, ModRevision, CreateRevision, and Lease. Key is the primary key. Saving grid edits generates put and del commands.

​
Command Editor

The editor accepts etcdctl-style commands with autocomplete for commands and flags.
etcd command editor with a get --prefix result grid

etcdctl-style commands in the editor

get supports --prefix, --limit=N, --keys-only, --order (ASCEND or DESCEND), and --sort-by (KEY, VERSION, CREATE, MOD, or VALUE). watch collects events for --timeout seconds (default 30), then returns them as a grid. Lease, cluster, and maintenance commands:
Lease IDs accept decimal or hex (0x prefix optional). Auth, user, and role management:

​
SSH Tunnel

etcd connections support SSH tunneling for reaching remote clusters through a bastion host.

​
Troubleshooting

Connection refused: Verify etcd is running and the client port (default 2379) is reachable. No supported etcd API found: TablePro requires the HTTP/JSON gateway, which etcd 3.x serves on the client port by default. Point the connection at the client port, not the peer port (2380). Authentication failed: Check the username and password, and that the user has the required roles. TLS errors: Set TLS Mode and the certificate paths in the Advanced fields. For self-signed certificates use Required (skip verify) or provide the CA certificate. Limitations: No transactions, no schema editing, and no import.