Clarify multiple load balancer scenario and LB configuration

[r0ckarong]

my idea was to explain how to use keepalived with two load balancers

but HA is literally another suse product, so we are conflicting there

my idea was for real HA you need two LB (you don't have a SPOF). With DNS you have my-cluster.company.corp that resolves to a VIP that is managed with keepalived in those two LB, when one is down the other uses the VIP, so you always use my-cluster.company.corp but you have a failure tolerant setup)

Markus Napp @mnapp 10:57 AM
ok but we need to tell people at least what they need to configure their load balancer for no?

Rafael Fernández López @ereslibre 10:57 AM
so, instead of going down the path of explaining how to do that we could just say "set up your LB or set of LB's as you'd do with any other service"
and state 3 masters + n workers for HA, plus the LB policy on your company
a note, that a single LB could be a single point of failure, and that more than one LB is desired

Markus Napp @mnapp 10:58 AM
yeah but "any other service" tells you what you need to configure or am I wrong? so how do I explain to people what their load balancers should be pointing at?

Rafael Fernández López @ereslibre 10:59 AM
this is a fair question and we should explain that load balancers for the apiservers should point to all apiservers, and perform https healthchecks as best practice (perform healthcheck doing https requests to apiservers on /healthz)
that way the LB will take out from the active pool those unresponsive apiservers automatically