HashiCorp’s general availability release of its https://www.hashicorp.com/blog/announcing-hashicorp-consul-api-gateway is intended to both simplify and tighten control of traffic and services management with HashiCorp Consul service mesh. However, a separate control plane had to be in place to control access from external requests from ingress traffic originating from the Internet.

In this way, the Consul API Gateway serves as a dedicated ingress for intelligently routing traffic to applications running on the HashiCorp Consul service mesh, https://ca.linkedin.com/in/brad-casemore-a64211, an analyst for IDC told The New Stack.

Consul API Gateway can thus be thought of as an extension of Consul service mesh.

In order to get started, users need to add the following block to their Helm values file in order to get started: “With Consul API Gateway, organizations are able to adopt a more consistent and controlled approach for exposing service mesh-based services to external clients, reducing the risk of a potential breach; increasing operational efficiency and reducing complexity by creating a single control plane for managing all traffic,” Casemore said.

Related Articles