consul

TLDR

Start agent in development mode

$ consul agent -dev

List datacenter members

$ consul members

Register service

$ consul services register [service.json]

Deregister service

$ consul services deregister -id=[service-id]

List services in catalog

$ consul catalog services

DNS lookup for service

$ dig @127.0.0.1 -p 8600 [web].service.consul

Store key-value pair

$ consul kv put [key] [value]

Get key-value

$ consul kv get [key]

Join cluster

$ consul join [192.168.1.100]

SYNOPSIS

consul [options] command [arguments]

consul is HashiCorp's service discovery and configuration tool. It provides service mesh, health checking, key/value storage, multi-datacenter support, and secure service-to-service communication.

PARAMETERS

-dev

Development mode (single node, no persistence)

-token token

ACL token for authentication

-datacenter dc

Target datacenter

-http-addr addr

Consul HTTP API address

COMMANDS

agent

Run a Consul agent

members

List cluster members

join

Join cluster via agent address

leave

Gracefully leave cluster

catalog

Interact with service catalog

services

Register/deregister services

Key/value store operations

connect

Service mesh functionality

acl

Access control list management

snapshot

Save/restore cluster state

debug

Create debugging archive

ENVIRONMENT

CONSUL_HTTP_ADDR

HTTP API address

CONSUL_HTTP_TOKEN

ACL token

CONSUL_CACERT

CA certificate path

DNS INTERFACE

Default DNS port: 8600

$ dig @127.0.0.1 -p 8600 web.service.consul

CAVEATS

ACL system requires token for most operations when enabled. Development mode stores everything in memory. Production requires proper clustering configuration.