I have a need for routing/loadbalance to a backend(s) based on subdomain names, terminate TLS/SSL, and support also websockets, (today I do this with HAproxy), I’am looking into Harvester to replace vmware based solutions (because of move from VM’s to containers - but both VM’s and docker containers will co-exist for some year(s))
I can ofc install a VM with haproxy and route through it (thats how its done today in my wmware environments). but I would really want to squeeze as much as possible out-of-the box from Harvester to reduce complexity and cpu/mem/traffic.
any thoughts are valuable
//Rickard