Consul 1.13 Introduces Cluster Peering
This release enhances a number of features in Consul while adding such new features as a Consul on Kubernetes CNI plugin and a beta version of cluster peering.
User Survey: How Do You Connect with Consul?
Want to earn some HashiCorp swag? Tell us about your Consul setup.
HashiCorp Consul Global Scale Benchmark
HashiCorp Consul updates 10,000 nodes and 172,000+ services in under 1 second in a new benchmark.
Creating a Kubernetes Cluster with AKS and Terraform
We are going to take a look at how we can create a Kubernetes cluster in Azure using the azurerm_kubernetes_cluster resource.
Making Gossip More Robust with Lifeguard
Today we are proud to announce our first publication by HashiCorp Research, titled "Lifeguard: SWIM-ing with Situational Awareness". The paper details a number of novel improvements we have introduced to Serf, Consul, and Nomad to make their underlying gossip protocol more robust. Collectively called Lifeguard, these extensions reduce by 50x the false positives produced by the failure detector and allow us to detect true failures faster. Distributed systems such as BitTorrent, Apache Cassandra, Microsoft Orleans, and HashiCorp Consul commonly use Gossip protocols. They are typically embedded to provide features such as cluster membership (who is in the cluster), failure detection (which members are alive), and event broadcast. Their peer to peer nature often makes them much more scalable and reliable than centralized approaches to solving the same problem. However, the reduced amount of communication makes them sensitive to slow processing of their messages. Many of our tools leverage work from the academic community, and with HashiCorp Research we hope to contribute back. Our focus is on novel work and whitepapers about the algorithms and system designs we are using in practice. Lifeguard is our first published work, and our users operating the tools in production environments drive the focus of these improvements. Read on to learn more about Lifeguard.