HAProxy Kubernetes Ingress Controller
Description
An ingress controller is a Kubernetes resource that routes traffic from outside your cluster to services within the cluster.
Detailed documentation can be found within the Official Documentation
Usage
Docker image is available on Docker Hub: haproxytech/kubernetes-ingress
If you prefer to build it from source use
docker build -t haproxytech/kubernetes-ingress -f build/Dockerfile .Please see controller.md for all available arguments of controler image.
Available customisations are described in doc
Basic setup to to run controller is described in yaml file.
kubectl apply -f deploy/haproxy-ingress.yamlHAProxy Helm Charts
Official HAProxy Technologies Helm Charts for deploying on Kubernetes are available in haproxytech/helm-charts repository
Contributing
Thanks for your interest in the project and your willing to contribute:
- Pull requests are welcome!
- For commit messages and general style please follow the haproxy project's CONTRIBUTING guide and use that where applicable.
- Please use
golangci-lint runfrom github.com/golangci/golangci-lint for linting code.
Discussion
A Github issue is the right place to discuss feature requests, bug reports or any other subject that needs tracking.
To ask questions, get some help or even have a little chat, you can join our #ingress-controller channel in HAProxy Community Slack.

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

