Search Results for "loadbalancer"

kube-vip provides Kubernetes clusters with a virtual IP and load balancer for both the control plane (for building a highly-available cluster) and Kubernetes Services of type LoadBalancer without relying on any external hardware or software. ARP is a layer 2 protocol that is used to inform the network of the location of a new address. When a new IP address is configured to a device, there needs to be a mechanism to inform the network of which piece of hardware is hosting this new address. ARP is the technology that is used to ensure that a network understands the link between the hardware address (MAC) and the logical address (IP).

Ingress controller implementation for HAProxy loadbalancer. HAProxy Ingress is a Kubernetes ingress controller: it configures a HAProxy instance to route incoming requests from an external network to the in-cluster applications. The routing configurations are built reading specs from the Kubernetes cluster. Updates made to the cluster are applied on the fly to the HAProxy instance.

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. Kubernetes defines many service constructs like cluster-ip, node-port, load-balancer etc for pod-to-pod, pod-to-service, and service from outside communication. All these services are provided by load balancers/proxies operating at Layer4/Layer7. Since Kubernetes's is highly modular, these services can...

...A Kubernetes ingress controller is an application that runs in a cluster and configures a load balancer based on Kubernetes resources (Ingress, HTTPRoute, TCPRoute, and more). Kong Ingress Controller configures Kong Gateway as a software load balancer that runs in the cluster and is typically exposed as a LoadBalancer service. Kong recommends using the Kong/ingress Helm chart to deploy the Kong Ingress Controller. This chart supports both DB-less and DB-backed deployments. If you’re not sure which to choose, we recommend choosing DB-less which treats the Kubernetes API server as the source of truth.

MetalLB is a load-balancer implementation for bare metal Kubernetes clusters, using standard routing protocols. Kubernetes does not offer an implementation of network load balancers (Services of type LoadBalancer) for bare-metal clusters. The implementations of network load balancers that Kubernetes does ship with are all glue code that calls out to various IaaS platforms (GCP, AWS, Azure…). If you’re not running on a supported IaaS platform (GCP, AWS, Azure…), LoadBalancers will remain in the “pending” state indefinitely when created. ...