We’ve released version 1.5 of the HAProxy Kubernetes Ingress Controller. This version unlocks access to the raw HAProxy configuration language for power users to gain more control. You can also enable mutual TLS authentication between the ingress controller and services, enforce Basic authentication, and return custom error pages to users.
The HAProxy Data Plane API 2.2 lays the foundation for first-class service discovery and introduces native support for Consul. It also adds storage and file handling for SSL certificates, Map files, and SPOE configuration files.
With HAProxy, you can implement a circuit breaker to protect services from widespread failure. Martin Fowler, who is famous for being one of the Gang of Four authors who wrote Design Patterns: Elements of Reusable Object-Oriented Software, hosts a website where he catalogues software design patterns. He defines the Circuit Breaker pattern like this: The basic idea behind the circuit breaker is very simple. You wrap a protected function call in a circuit breaker object, which monitors for failures.
Route SSH connections through HAProxy using the SSH ProxyCommand feature and SNI. Did you know that you can proxy SSH connections through HAProxy and route based on hostname? The advantage is that you can relay all SSH traffic through one public-facing server instead of needing to grant users direct access to potentially hundreds of internal servers from outside the network.
Persistent connections allow HAProxy to optimize resource usage, lower latency on both the client and server side, and support connection pooling. HTTP is a layer 7 protocol that’s transmitted over a TCP connection. It works in a client-server model and follows the request-response paradigm, which means that a client sends a request to a server, which then replies with a response. From this statement, you can infer two different ways of operating.
With the second wave of coronavirus sweeping across the nation, experts predict a greater percentage of this year’s holiday shopping to be conducted online than ever before. In fact, a recent National Retail Federation Holiday 2020 survey predicts that “digital purchases will be the primary driver of growth this year” with 96% of respondents expecting more online-only holiday sales as consumers are less likely to visit actual stores.
Log Sampling is a powerful feature introduced in HAProxy 2.0 that lets you define a percentage of your logs to create a representative view of your data allowing you to minimize your costs. Log files are the key to observability. They can provide helpful information that can be used for debugging as well as analytics that can be used to understand how users interact with an application.
HAProxy can run in two different modes: TCP or HTTP. When operating in TCP mode, we say that it acts as a layer 4 proxy. In HTTP mode, we say that it acts as a layer 7 proxy. To understand the difference, you must first learn about the Open Systems Interconnection (OSI) model, which helps IT pros conceptualize and explain where a piece of software fits in the context of a computer network.
VMware chose HAProxy as the default load balancer for Tanzu Kubernetes clusters, which helped streamline load balancing in their Kubernetes platform. VMware has delivered vSphere 7 with Tanzu, its endeavor to embed an enterprise-grade version of Kubernetes inside vSphere, the industry-leading compute virtualization platform.
