Kubernetes ingress controler with OpenResty
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
config/default fix healthcheck Apr 16, 2018
controller Fix multiple rules causing duuplicate paths Jun 20, 2018
manifests update DS manifest Apr 22, 2018
template fix template Apr 28, 2018
vendor Initial commit Apr 15, 2018
.gitignore Initial commit Apr 15, 2018
.travis.yml add tag release Apr 22, 2018
Dockerfile add dumy cert Apr 15, 2018
Gopkg.lock Initial commit Apr 15, 2018
Gopkg.toml Initial commit Apr 15, 2018
LICENSE Initial commit Apr 15, 2018
README.md Initial commit Apr 15, 2018


Kubernetes OpenResty Ingress Controller

Why OpenResty?

I work in an high traffic envoirement where we have tested different reverse proxies. Our tests showed NGINX as the best one on resource usage. But NGINX didn't fit our needs ins customisability, that is why we chose OpenResty as a solution. While this setup is quite minimal we have more stuff going on in our production configuration.

Why not the NGINX ingress controller

We wanted a minimalistic ingress controller setup. By browsing through the code of the NGINX ingress controller I got an impression of added complexity. Plus it is a nice learning experience as it seems not many people write their own ingress controller.

Can I just use this with X

Probably yes, in order to allow flexible configuration options this used Go Templating. It should be easy to port this to the reverse proxy of your choise.

Thank you to

  • traefik For having understandable code on the Kubernetes backend