Skip to content
Go to file


Failed to load latest commit information.
Latest commit message
Commit time
Apr 28, 2018
Apr 15, 2018
Apr 15, 2018
Apr 15, 2018
Apr 15, 2018
Apr 15, 2018
Apr 15, 2018
May 17, 2020

No longer maintained

I do no longer maintain this project, if you are interested in using it I reccomend forking it. There is a fork of this that uses a redis backend to talk to OpenResty which is still maintained, you can find it at

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


Kubernetes ingress controler with OpenResty




No packages published