base on eBPF based cloud-native load-balancer for Kubernetes|Edge|Telco|IoT|XaaS.  [](https://www.loxilb.io) [](https://ebpf.io/projects#loxilb) [](https://goreportcard.com/report/github.com/loxilb-io/loxilb) [](https://www.bestpractices.dev/projects/8472)    [![Info][docs-shield]][docs-url] [](https://join.slack.com/t/loxilb/shared_invite/zt-2b3xx14wg-P7WHj5C~OEON_jviF0ghcQ) ## What is loxilb loxilb is an open source cloud-native load-balancer based on GoLang/eBPF with the goal of achieving cross-compatibility across a wide range of on-prem, public-cloud or hybrid K8s environments. loxilb is being developed to support the adoption of cloud-native tech in telco, mobility, and edge computing. ## Kubernetes with loxilb Kubernetes defines many service constructs like cluster-ip, node-port, load-balancer, ingress etc for pod to pod, pod to service and outside-world to service communication.  All these services are provided by load-balancers/proxies operating at Layer4/Layer7. Since Kubernetes is highly modular, these services can be provided by different software modules. For example, kube-proxy is used by default to provide cluster-ip and node-port services. For some services like LB and Ingress, no default is usually provided. Service type load-balancer is usually provided by public cloud-provider(s) as a managed entity. But for on-prem and self-managed clusters, there are only a few good options available. Even for provider-managed K8s like EKS, there are many who would want to bring their own LB to clusters running anywhere. Additionally, Telco 5G and edge services introduce unique challenges due to the variety of exotic protocols involved, including GTP, SCTP, SRv6, SEPP, and DTLS, making seamless integration particularly challenging. <b>loxilb provides service type load-balancer as its main use-case</b>. loxilb can be run in-cluster or ext-to-cluster as per user need. loxilb works as a L4 load-balancer/service-proxy by default. Although L4 load-balancing provides great performance and functionality, an equally performant L7 load-balancer is also necessary in K8s for various use-cases. loxilb also supports L7 load-balancing in the form of Kubernetes Ingress implementation which is enhanced with eBPF sockmap helpers. This also benefit users who need L4 and L7 load-balancing under the same hood. Additionally, loxilb also supports: - [x] kube-proxy replacement with eBPF(full cluster-mesh implementation for Kubernetes) - [x] Ingress Support - [x] Kubernetes Gateway API - [ ] Kubernetes Network Policies ## Telco-Cloud with loxilb For deploying telco-cloud with cloud-native functions, loxilb can be used as an enhanced SCP(service communication proxy). SCP is a communication proxy defined by [3GPP](https://www.etsi.org/deliver/etsi_ts/129500_129599/129500/16.04.00_60/ts_129500v160400p.pdf) and aimed at telco micro-services running in cloud-native environment. Read more in this [blog](https://dev.to/nikhilmalik/5g-service-communication-proxy-with-loxilb-4242)  Telco-cloud requires load-balancing and communication across various interfaces/standards like N2, N4, E2(ORAN), S6x, 5GLAN, GTP etc. Each of these present its own unique challenges which loxilb aims to solve e.g.: - N4 requires PFCP level session-intelligence - N2 requires NGAP parsing capability(Related Blogs - [Blog-1](https://www.loxilb.io/post/ngap-load-balancing-with-loxilb), [Blog-2](https://futuredon.medium.com/5g-sctp-loadbalancer-using-loxilb-b525198a9103), [Blog-3](https://medium.com/@ben0978327139/5g-sctp-loadbalancer-using-loxilb-applying-on-free5gc-b5c05bb723f0)) - S6x requires Diameter/SCTP multi-homing LB support(Related [Blog](https://www.loxilb.io/post/k8s-introducing-sctp-multihoming-functionality-with-loxilb)) - MEC use-cases might require UL-CL understanding(Related [Blog](https://futuredon.medium.com/5g-uplink-classifier-using-loxilb-7593a4d66f4c)) - Hitless failover support might be essential for mission-critical applications - E2 might require SCTP-LB with OpenVPN bundled together - SIP support is needed to enable cloud-native VOIP - N32 requires support for Security Edge Protection Proxy(SEPP) ## Why choose loxilb? - ```Performs``` much better compared to its competitors across various architectures * [Single-Node Performance](https://loxilb-io.github.io/loxilbdocs/perf-single/) * [Multi-Node Performance](https://loxilb-io.github.io/loxilbdocs/perf-multi/) * [Performance on ARM](https://www.loxilb.io/post/running-loxilb-on-aws-graviton2-based-ec2-instance) * [Short Demo on Performance](https://www.youtube.com/watch?v=MJXcM0x6IeQ) - Utilizes ebpf which makes it ```flexible``` as well as ```customizable``` - Advanced ```quality of service``` for workloads (per LB, per end-point or per client) - Works with ```any``` Kubernetes distribution/CNI - k8s/k3s/k0s/kind/OpenShift + Calico/Flannel/Cilium/Weave/Multus etc - Kube-proxy replacement with loxilb allows ```simple plug-in``` with any existing/deployed pod-networking software - Extensive support for ```SCTP workloads``` (with multi-homing) on K8s - Dual stack with ```NAT66, NAT64``` support for K8s - K8s ```multi-cluster``` support (planned 🚧) - Runs in ```any``` cloud (public cloud/on-prem) or ```standalone``` environments ## Overall features of loxilb - L4/NAT stateful loadbalancer * NAT44, NAT66, NAT64 with One-ARM, FullNAT, DSR etc * Support for TCP, UDP, SCTP (w/ multi-homing), QUIC, FTP, TFTP etc - High-availability support with BFD detection for hitless/maglev/cgnat clustering - Extensive and scalable end-point liveness probes for cloud-native environments - Stateful firewalling and IPSEC/Wireguard support - Optimized implementation for features like [Conntrack](https://thermalcircle.de/doku.php?id=blog:linux:connection_tracking_1_modules_and_hooks), QoS, etc - Full compatibility for ipvs (ipvs policies can be auto inherited) - Policy oriented L7 proxy support - HTTP1.0, 1.1, 2.0, 3.0 ## Components of loxilb - GoLang based control plane components - A scalable/efficient [eBPF](https://ebpf.io/) based data-path implementation - Integrated goBGP based routing stack - A kubernetes operator [kube-loxilb](https://github.com/loxilb-io/kube-loxilb) written in Go - A kubernetes ingress [implementation](https://github.com/loxilb-io/loxilb-ingress) ## Architectural Considerations - [Understanding loxilb modes and deployment in K8s with kube-loxilb](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/kube-loxilb.md) - [Understanding High-availability with loxilb](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/ha-deploy.md) ## Getting Started #### loxilb as ext-cluster pod - [K8s : loxilb ext-mode](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/k8s-flannel-ext.md) - [K3s : loxilb with default flannel](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/k3s_quick_start_flannel.md) - [K3s : loxilb with calico](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/k3s_quick_start_calico.md) - [K3s : loxilb with cilium](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/quick_start_with_cilium.md) - [K0s : loxilb with default kube-router networking](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/k0s_quick_start.md) - [EKS : loxilb ext-mode](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/eks-external.md) #### loxilb as in-cluster pod - [K8s : loxilb in-cluster mode](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/k8s-flannel-incluster.md) - [K3s : loxilb in-cluster mode](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/k3s_quick_start_incluster.md) - [K0s : loxilb in-cluster mode](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/k0s_quick_start_incluster.md) - [MicroK8s : loxilb in-cluster mode](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/microk8s_quick_start_incluster.md) - [EKS : loxilb in-cluster mode](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/eks-incluster.md) - [RedHat OCP : loxilb in-cluster mode](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/rhocp-quickstart-incluster.md) #### loxilb as service-proxy (kube-proxy replacement) - [K3s : loxilb service-proxy with flannel](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/service-proxy-flannel.md) - [K3s : loxilb service-proxy with calico](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/service-proxy-calico.md) #### loxilb as Kubernetes Ingress - [K3s: How to run loxilb-ingress](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/loxilb-ingress.md) #### loxilb in standalone mode - [Run loxilb standalone](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/standalone.md) ## Advanced Guides - [How-To : Service-group zones with loxilb](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/service-zones.md) - [How-To : Access end-points outside K8s](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/ext-ep.md) - [How-To : Deploy multi-server K3s HA with loxilb](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/k3s-multi-master.md) - [How-To : Deploy loxilb with multi-AZ HA support in AWS](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/aws-multi-az.md) - [How-To : Deploy loxilb with multi-cloud HA support](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/multi-cloud-ha.md) - [How-To : Deploy loxilb with ingress-nginx](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/loxilb-nginx-ingress.md) - [How-To : Run loxilb in-cluster with secondary networks](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/loxilb-incluster-multus.md) - [How-To : Kubernetes service sharding with loxilb](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/service-sharding.md) - [How-To : loxilb L4/L7 Load-Balancing with Kubernetes Gateway API](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/gw-api.md) ## Knowledge-Base - [What is eBPF](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/ebpf.md) - [What is k8s service - load-balancer](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/lb.md) - [Architecture in brief](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/arch.md) - [Code organization](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/code.md) - [eBPF internals of loxilb](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/loxilbebpf.md) - [What are loxilb NAT Modes](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/nat.md) - [loxilb load-balancer algorithms](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/lb-algo.md) - [Manual steps to build/run](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/run.md) - [Debugging loxilb](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/debugging.md) - [loxicmd command-line tool usage](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/cmd.md) - [Developer's guide to loxicmd](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/cmd-dev.md) - [Developer's guide to loxilb API](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/api-dev.md) - [HTTPS guide for loxilb API](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/https.md) - [API Reference - loxilb web-Api](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/api.md) - [Performance Reports](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/perf.md) - [Development Roadmap](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/roadmap.md) - [Contribute](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/contribute.md) - [System Requirements](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/requirements.md) - [Frequently Asked Questions- FAQs](https://github.com/loxilb-io/loxilbdocs/blob/main/docs/faq.md) - [Blogs](https://www.loxilb.io/blog) - [Demo Videos](https://www.youtube.com/@loxilb697) ## Community ### Slack Join the loxilb [Slack](https://www.loxilb.io/members) channel to chat with loxilb developers and other loxilb users. This is a good place to learn about loxilb, ask questions, and work collaboratively. ### General Discussion Feel free to post your queries in github [discussion](https://github.com/loxilb-io/loxilb/discussions). If you find any issue/bugs, please raise an [issue](https://github.com/loxilb-io/loxilb/issues) in github and members from loxilb community will be happy to help. ### Community Posts - [5G SCTP Load Balancer using LoxiLB](https://futuredon.medium.com/5g-sctp-loadbalancer-using-loxilb-b525198a9103) - [5G Uplink Classifier using LoxiLB](https://futuredon.medium.com/5g-uplink-classifier-using-loxilb-7593a4d66f4c) - [5G SCTP Load Balancer with free5gc](https://medium.com/@ben0978327139/5g-sctp-loadbalancer-using-loxilb-applying-on-free5gc-b5c05bb723f0) - [K8s - Bring load balancing to Multus workloads with LoxiLB](https://cloudybytes.medium.com/k8s-bringing-load-balancing-to-multus-workloads-with-loxilb-a0746f270abe) - [K3s - Using LoxiLB as External Service Load Balancer](https://cloudybytes.medium.com/k3s-using-loxilb-as-external-service-lb-2ea4ce61e159) - [Kubernetes Services - Achieving Optimal performance is elusive](https://cloudybytes.medium.com/kubernetes-services-achieving-optimal-performance-is-elusive-5def5183c281) ## CICD Workflow Status | Features(Ubuntu20.04) | Features(Ubuntu22.04)| Features(Ubuntu24.04)| Features(RedHat9)| |:----------|:-------------|:-------------|:-------------| | [](https://github.com/loxilb-io/loxilb/actions/workflows/docker-image.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/docker-multiarch.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/docker-multiarch.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/docker-multiarch.yml) | | [](https://github.com/loxilb-io/loxilb/actions/workflows/basic-sanity.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/basic-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/basic-sanity-ubuntu-24.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/basic-sanity-rh9.yml) | | [](https://github.com/loxilb-io/loxilb/actions/workflows/tcp-sanity.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/tcp-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/tcp-sanity-ubuntu-24.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/tcp-sanity-rh9.yml) | | [](https://github.com/loxilb-io/loxilb/actions/workflows/udp-sanity.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/udp-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/udp-sanity-ubuntu-24.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/udp-sanity-rh9.yml) | | [](https://github.com/loxilb-io/loxilb/actions/workflows/sctp-sanity.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/sctp-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/sctp-sanity-ubuntu-24.yml) |[](https://github.com/loxilb-io/loxilb/actions/workflows/sctp-sanity-rh9.yml) | | [](https://github.com/loxilb-io/loxilb/actions/workflows/advanced-lb-sanity.yml)| [](https://github.com/loxilb-io/loxilb/actions/workflows/advanced-lb-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/advanced-lb-sanity-ubuntu-24.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/advanced-lb-sanity-rh9.yml)| | [](https://github.com/loxilb-io/loxilb/actions/workflows/nat66-sanity.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/nat66-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/nat66-sanity-ubuntu-24.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/nat66-sanity-rh9.yml) | | [](https://github.com/loxilb-io/loxilb/actions/workflows/ipsec-sanity.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/ipsec-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/ipsec-sanity-ubuntu-24.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/ipsec-sanity-rh9.yml) | | [](https://github.com/loxilb-io/loxilb/actions/workflows/liveness-sanity.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/liveness-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/liveness-sanity-ubuntu-24.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/liveness-sanity-rh9.yml) | | | [](https://github.com/loxilb-io/loxilb/actions/workflows/scale-sanity-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/scale-sanity-ubuntu-24.yml) | | |[](https://github.com/loxilb-io/loxilb/actions/workflows/perf.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/perf.yml) |[](https://github.com/loxilb-io/loxilb/actions/workflows/perf.yml) | | | K3s Tests | K8s Cluster Tests | EKS Test | |:-------------|:-------------|:-------------| |[](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-base-sanity.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/k8s-calico-ipvs.yml) |  | | [](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-flannel.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/k8s-calico-ipvs2.yml) | | | [](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-flannel-ubuntu-22.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/k8s-calico-ipvs3.yml) | | |[](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-flannel-cluster.yml) | [](https://github.com/loxilb-io/loxilb/actions/workflows/k8s-calico-ipvs3-ha.yml) | | | [](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-flannel-incluster.yml) | | | |[](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-flannel-incluster-l2.yml) | | | | [](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-calico.yml) | | | | [](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-cilium-cluster.yml) | | | [](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-sctpmh.yml) | | | | [](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-sctpmh-ubuntu22.yml) | | | | [](https://github.com/loxilb-io/loxilb/actions/workflows/k3s-sctpmh-2.yml) | | | ## 📚 Please check loxilb [website](https://www.loxilb.io) for more detailed info. [docs-shield]: https://img.shields.io/badge/info-docs-blue [docs-url]: https://loxilb-io.github.io/loxilbdocs/ [slack=shield]: https://img.shields.io/badge/Community-Join%20Slack-blue [slack-url]: https://www.loxilb.io/members ", Assign "at most 3 tags" to the expected json: {"id":"6947","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"