Open wingsuitist opened 3 months ago
I tried a long time ago to put many clusters behind a haproxy via "cluster domain" based routing. And I failed, there were some strange errors. That's why I decided to go with additional IPs. If you can provide a reliable solution, we can add a new docs part how to set it up or an add-on.
I'm not pretty sure how many users who really need. Most of the users I know have just one cluster running.
We are currently evaluating if we can use it to spin up a clusters for a few days or just hours, and then destroy it again. Mostly for integration testing, but also for experiments where we quickly need a clean setup, and can not do the experiment on the same cluster as other experiments. Hope we can find the time to solve it.
=> About the errors: Was ist also problematic for the whole "*apps.xyz" part or only for the api?
I cannot remember, might be API only because of client cert auth.
Possibility for multiple clusters with one IP.
Scenario 10 clusters:
Main Domain: example.com
API using different ports:
Todo: Check if reverse proxy can reliably handle API calls using different host names or if different ports are required.
Apps:
Possible solutions: