[k4k4]

Ok, HAProxy is a potential solution, but according to the description I posted, the idea behind this project is to reduce the writing of configuration files. Instead of writing an elaborate conf, just provide two JSONs to achieve the same thing. And yes I am aware of the fact that solutions like Apache, HaProxy and NginX are more popular and preferred for large solutions. I do not want to create yet another miracle product in well researched matter. But I am grateful for the feedback :)

[stephenr]

Ah yes, how silly of me. Writing two config files in fucking JSON of all things is absolutely better than writing one config file.

[k4k4]

Firstly, you don't have to be rude. I won't fall for this bait. Secondly, if you are tied to writing one configuration file, I understand, after all you have a free choice. For me, the separation of logic is a positive aspect, because I don't have to think and search for entries about the specific server I'm proxying to. JSONs used here are overcomplicated I see. And the difficulty of mounting configuration files from ConfigMap with one file or two is practically the same - yet with this software you store two files in ConfigMap. I understood from your post that you are a HAProxy fanatic and I won't bother you in any way.

[besprim17]

Didn't you read the description? This is written by an amateur probably as the first major open source project. It is intended to be an alternative to (the configuration of) known and used solutions. The fact that the author came up with two jsons.... just accept it?