Consul

Purpose

Deploy and operate HashiCorp Consul for service discovery, health checking, KV configuration, multi-datacenter federation, and the Connect service mesh with mTLS, intentions, and Envoy proxying.

Agent Protocol

Trigger

Exact user phrases: "consul", "consul agent", "consul server", "consul client", "consul cluster", "consul datacenter", "consul service discovery", "consul DNS", "consul catalog", "consul health check", "consul KV", "consul sessions", "consul ACL", "consul token", "consul connect", "consul service mesh", "consul intention", "consul envoy", "consul mesh gateway", "consul snapshot", "consul federation", "consul admin partition", "consul namespace", "consul k8s", "consul helm", "consul terraform", "consul-template", "consul ESM", "consul NIA", "consul terraform sync", "service discovery".

Input Context

• Consul deployment topology (single or multiple datacenters).
• Agent modes: server, client, or dev (local).
• Integration points: Nomad, Vault, Terraform, Kubernetes, Envoy, registrator.
• Networking: gossip (8301/8302) and RPC (8300) port layouts, TLS, mTLS mesh.
• Scale expectations: number of services, registers per second, queries per second.

Output Artifact

Consul agent configuration (HCL), service registration definitions, ACL policy/token files, intention rules, or Terraform/Kubernetes manifests.