
agentgateway
7.5#4 in kubernetes ingress controllersFree planFree planWebAPILinuxmacOS
Visit

| Fact | agentgateway | HAProxy Ingress |
|---|---|---|
| Deployment | The project provides standalone binary, Docker and Kubernetes deployment paths. | The controller is installed and configured with a Helm chart, and the instructions require Helm version 3. |
| Purpose | Agentgateway is an open-source HTTP and gRPC gateway for routing, securing, observing, and governing service, LLM, MCP, and agent-to-agent traffic. | HAProxy Ingress configures HAProxy to route incoming requests from an external network to applications in a Kubernetes cluster. |
| Security | Listed security features include JWT and OIDC, API keys, authorization policies, TLS and mTLS with certificate rotation, and rate limiting. | The getting-started guide says HAProxy Ingress uses TLS SNI and the Host header to associate requests with ingress hosts. |
| Support | The enterprise page lists partner-provided commercial support, including a Solo.io offer with 24×7 coverage, upstream collaboration, and best-practice guidance. | The project lists a Kubernetes Slack channel, a users mailing list, and Stack Overflow for community discussion and questions. |
Agentgateway is aimed at platform engineers, tool-builders, and AI enthusiasts who need self-hosted traffic controls for services, LLMs, or agent systems. It also suits platform teams seeking routing, security, and observability features in one gateway.
HAProxy Ingress suits operators configuring HAProxy to route traffic to applications in Kubernetes. It requires cluster administration privileges and may suit users who can work within the documented partial Gateway API support.