AWS Elastic Load Balancing vs OpenELB

AWS Elastic Load Balancing distributes incoming application traffic across targets and virtual appliances in one or more Availability Zones. It offers Application, Network, Gateway, and Classic Load Balancers, scales request handling with traffic, and runs configurable health checks on targets. Application Load Balancers support HTTP header-based routing, redirects, fixed responses, HTTP/2, and gRPC. Network Load Balancers support static Elastic IP addresses and AWS PrivateLink for TCP and TLS listeners. The service also supports SSL/TLS termination, certificate management, and client certificate authentication. CloudWatch metrics and logging are available for all four types. A single load balancer can distribute traffic across AWS and on-premises resources. Kubernetes support includes direct-to-pod routing for Application Load Balancers and private EKS clusters for Application and Network Load Balancers. AWS recommends different types for HTTP, transport protocols, third-party virtual appliances, and EC2-Classic applications. Usage charges vary by region; data transfer and public IPv4 address charges may be additional. New AWS customers receive a free tier for six months after account creation, with usage limits and up to $200 in credits.

OpenELB exposes Kubernetes LoadBalancer services externally in bare-metal, edge, and virtualization environments. It assigns service addresses from Eip-managed IP pools and supports BGP, Layer 2, and VIP load-balancing modes. BGP mode uses GoBGP to publish routes to peer routers and supports ECMP, while BgpConf and BgpPeer custom resources configure BGP properties. Layer 2 mode requires infrastructure that permits anonymous ARP/NDP packets. VIP mode uses VRRP for high availability. OpenELB can be installed with kubectl manifests or Helm 3 in Kubernetes 1.15 or later, and guides are listed for Kubernetes, K3s, and KubeSphere. The project currently supports IPv4 only and is not a managed service. Layer 2 and VIP modes forward through one active node, so failover can briefly interrupt services and bandwidth is limited by that node. BGP requires a router supporting BGP and ECMP. OpenELB uses Apache License 2.0.