eBPF will help solve service mesh by getting rid of sidecars

Re:eBPF will help solve service mesh by getting rid of sidecars by dharmab on Thursday December 09, 2021 @04:02PM (#29502891)

If you're asking about connection stability in general:

- Ideally, you avoid it in your application design.

- If you need it, you set up SIGTERM handling in the application to wait for all connections to close before the process exits. You also set up "connection draining" at the load balancer to keep existing sessions to terminating Pods open but send new sessions to the new Pods. The tradeoff is that rollouts take much longer- if the session time is unbounded, you may need to enforce a deadline to break connections eventua.

[ Parent | on HN ]

Re:eBPF will help solve service mesh by getting rid of sidecars by dilyevsky on Thursday December 09, 2021 @05:14PM (#29503711)

You dont just wait until all connections exit, you first need to withdraw bgp announcement to the edge router, then start the wait. It’s not that simple with metal LBs. On the other hand it’s not that simple with cloud LBs either bc they also break long tcp streams when they please

[ Parent | on HN ]

Re:eBPF will help solve service mesh by getting rid of sidecars by dharmab on Friday December 10, 2021 @12:58AM (#29506872)

We reused the LB as much as possible to avoid the BGP thing. There's a thing called MetalLB designed around that though.

https://metallb.universe.tf/

[ Parent | on HN ]

Re:eBPF will help solve service mesh by getting rid of sidecars by dilyevsky on Saturday December 11, 2021 @02:32PM (#29523531)

Pretty sure metallb will have same problem when you need to rotate nodes in bgp mode

[ Parent | on HN ]