Servers: Load Balancing, eBPF, and Kubernetes
-
Load Balancing
Past a certain point, web applications outgrow a single server deployment. Companies either want to increase their availability, scalability, or both! To do this, they deploy their application across multiple servers with a load balancer in front to distribute incoming requests. Big companies may need thousands of servers running their web application to handle the load.
In this post we're going to focus on the ways that a single load balancer might distribute HTTP requests to a set of servers. We'll start from the bottom and work our way up to modern load balancing algorithms.
-
Sidecarless eBPF service mesh sparks debate
Service mesh products from Isovalent and Solo.io branched out this week beyond Kubernetes, but an underlying battle over the role of eBPF and the future of service mesh architectures raged on at KubeCon + CloudNativeCon Europe.
Isovalent, the commercial backers of the Cilium networking project based on the extended Berkeley Packet Filter (eBPF) Linux kernel utility, rolled out Cilium Mesh this week, a companion to the Cilium Service Mesh that links with resources outside Kubernetes. Not to be outdone, Istio service mesh platform vendor Solo.io launched Gloo Fabric, which supports multi-cloud network management for VM-based and serverless workloads in addition to containers and Kubernetes.
-
Logz.io Enhances Kubernetes 360 with Security Scanning Integration [Ed: Has SJVN become a 'Linux' Foundation drone for proprietary disservices?]
Logz announced this at KubeCon Europe. They're doing this by integrating its service with Aqua Trivy, the popular open-source vulnerability, and misconfiguration scanning solution. This enhancement will enable 360 platform users to promptly identify and resolve security issues in their Kubernetes environments. Trivy specifically scans for issues in open-source packages and dependencies, infrastructure as code, misconfigurations, and Common Vulnerabilities and Exposures (CVEs).