API gateway is stale

[Sharofiddin]

Consul’s API Gateway for Kubernetes feels stale and significantly behind modern Gateway API–based solutions, yet once you adopt Consul as a service mesh you’re effectively forced to use it for first-class north–south traffic. This creates a real architectural dead end: teams want Consul Mesh but also need a modern, fast-evolving API gateway, and today there’s no clear, supported way to combine Consul Mesh with third-party gateways without losing integration, observability, or supportability. Is Consul’s API Gateway actively evolving toward feature parity, or is HashiCorp intentionally coupling the mesh to a single gateway implementation? A clear stance or roadmap here would help teams decide whether Consul remains a viable long-term choice.