<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HAproxy on Blog · Muhammad Fauzi Islami</title><link>https://fauzislami.github.io/tags/haproxy/</link><description>Recent content in HAproxy on Blog · Muhammad Fauzi Islami</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 17 Oct 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://fauzislami.github.io/tags/haproxy/index.xml" rel="self" type="application/rss+xml"/><item><title>Highly Available Kubernetes Cluster Using HAproxy and Keepalived</title><link>https://fauzislami.github.io/blog/2021/10/17/highly-available-kubernetes-cluster-with-haproxy-and-keepalived/</link><pubDate>Sun, 17 Oct 2021 00:00:00 +0000</pubDate><guid>https://fauzislami.github.io/blog/2021/10/17/highly-available-kubernetes-cluster-with-haproxy-and-keepalived/</guid><description>&lt;p&gt;Kubernetes provides us a convenient way to make our application easier to maintain and more scalable. Since kubernetes is only an abstraction that runs on a set of machines and consists of many components, we have some work to do to keep our kubernetes cluster well-established and healthy, especially to make that cluster highly available. In this case, I use two HAproxy instances to balance the load over the network or we usually say that as load balancing. Not only that, I also use Keepalived which will make it redundant between the two HAproxy instances. The diagram below depicts how HAproxy and Keepalived play their role :&lt;/p&gt;</description></item></channel></rss>