LEARN. PRACTICE. GROW.Concept and mechanism
Gateways perform different functions. API gateway receives external traffic for mesh services; terminating gateway supports reaching external services from the mesh; mesh gateway supports connectivity across datacenters or partitions according to design. Ingress gateway appears in older material but is deprecated and documentation recommends API gateway as an alternative. Selection must consider identity, TLS, routes, and operation on each segment including the final connection to a legacy system. Do not assume any gateway makes every internal and external destination equivalent. Draw source, destination, termination points, and ownership of certificates and rules.
Guided application
Cluster peering connects independent clusters. Establishing a connection does not automatically export every service or authorize every communication. Define exports, peers, and required intentions rather than treating it as general KV copying or Raft-set merging. For a new project, confirm edition and version before promising capabilities. The current consulted matrix limits Community mesh to one cluster and distinguishes Standard Enterprise from Premium. Historical material may describe different availability, so blueprint 003 does not prove current licensing. In a fictional example, the PM should include cost, network dependencies, inter-site failure exercises, and RUN ownership in the approved design before assuming peering solves business recovery.
Active peering with an unexported service: control connectivity does not demonstrate service availability.
Common pitfalls
Gateway as one universal function; peering as replicated KV; old tutorial as current contract.
Related topics: Discovery, architecture, and quorum · Deployment and bootstrap · Registration, health checks, and DNS
Validate the entire path and the chosen edition’s entitlements.
Reference: Consul gateway roles · Historical Consul Associate (003), retired 2026-07-15; technical references inspected 2026-09-30