News for hackers. Stuff that matters.

A comment on eBPF will help solve service mesh by getting rid of sidecars. Parent comment

Re:eBPF will help solve service mesh by getting rid of sidecars by dharmab on Thursday December 09, 2021 @01:13PM (#29500881)
> May I ask what one might use in an AWS cloud environment to provide that load balancer within a Region?

The AWS cloud controller will automatically set up an ALB for you if you configure a LoadBalancer service in Kubernetes. I've also done custom setups with AWS NLBs.

> Does IPv6 address any of these issues?

It could address some issues- you could conceivably create a CNI plugin which allocates an externally addressable IP to your Pods. Although you would probably still want a load balancer for custom routing rules and the improved reliability over DNS round robin.

[ Parent | on HN ]
Re:eBPF will help solve service mesh by getting rid of sidecars by topspin on Thursday December 09, 2021 @10:58PM (#29506236)
Are ALB/NLB employed to handle traffic between pods in the same cluster? Or have I misunderstood the whole discussion?

My take on the 'eBPF will help solve service mesh' proposal is that it deals with not only ingress/egress traffic (where ALB/NLB are typically employed) but all traffic, including traffic between pods in a cluster. This is where my interests lay.

[ Parent | on HN ]
Re:eBPF will help solve service mesh by getting rid of sidecars by dharmab on Friday December 10, 2021 @01:17AM (#29506948)
> Are ALB/NLB employed to handle traffic between pods in the same cluster?

You can choose to do so, or you can communicate directly via the built-in Kubernetes service discovery and CNI overlay network. There are use cases for both.

[ Parent | on HN ]