HAProxy Ingress
5.7#15 in kubernetes ingress controllersFree planFree planLinuxSelf-hosted
VisitHAProxy Ingress vs Higress
What both publish
| Fact | HAProxy Ingress | Higress |
|---|---|---|
| Deployment | The controller is installed and configured with a Helm chart, and the instructions require Helm version 3. | A Docker all-in-one deployment exposes the console on port 8001, HTTP gateway on 8080 and HTTPS gateway on 8443. |
| Security | The getting-started guide says HAProxy Ingress uses TLS SNI and the Host header to associate requests with ingress hosts. | Listed protections include prompt-attack detection, sensitive-content identification, data privacy protection, and output-content filtering. |
| Support | The project lists a Kubernetes Slack channel, a users mailing list, and Stack Overflow for community discussion and questions. | The community edition includes community support and documentation; the dedicated commercial edition lists ticket, DingTalk group, and offline support. |
HAProxy Ingress plans
- HAProxy IngressFree
Higress plans
- Alibaba Cloud AI Gateway Serverless StandardPriced on request
- Higress CommunityFree
- Higress Community EditionFree
- Alibaba Cloud AI Gateway Serverless EnterprisePriced on request
- Feitian Exclusive EditionPriced on request
Pick HAProxy Ingress if…
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.
Pick Higress if…
Higress suits teams that need a self-hosted gateway for AI services and cloud-native traffic. It may also fit those needing MCP, Kubernetes gateway, or API lifecycle capabilities.