Live data from Hacker News

Kubernetes Failure Stories

srcco.de

241–242 of 242 posts

Re: Kubernetes Failure Stories

#241
post #240
post #239

Earlier quoted context omitted.

The haproxy method doesn't rely on DNS at all so I'm a bit confused.

well either it uses DNS for failover or you have ipvs (lvs, keepalived) enabled or worse if the machine with haproxy crashes your basically dead. Of course there is also bgp and anycast, but this is not "cheap"

That's not how it works. It is very similar to sidecar approach which various service discovery solutions have. You have haproxy running locally on localhost and you communicate with it, the haproxy then routes the request to right nodes. No DNS, no LVS and no keepalived.

Re: Kubernetes Failure Stories

#242
post #241
post #240

Earlier quoted context omitted.

well either it uses DNS for failover or you have ipvs (lvs, keepalived) enabled or worse if the machine with haproxy crashes your basically dead. Of course there is also bgp and anycast, but this is not "cheap"

That's not how it works. It is very similar to sidecar approach which various service discovery solutions have. You have haproxy running locally on localhost and you communicate with it, the haproxy then routes the request to right nodes. No DNS, no LVS and no keepalived.

well I've talked about edge Load Balancing..
Post reply on HN