HashiCorp Cloud Platform (HCP) Consul is moving into general availability. In this blog, we’ll show users how they can get started consuming Consul as a managed offering in AWS.
HashiCorp Consul Service on Azure now offers federation between HCS datacenters as a preview feature.
HashiCorp Consul Service (HCS) on Azure can be launched directly from the Azure Portal, but you can also manage HCS using Terraform Cloud.
In this video, we demonstrate how HashiCorp Consul allows operators to quickly connect applications across multiple clouds (on-premises, Google Cloud, Amazon AWS) as well as multiple runtime environments (Virtual Machine, Kubernetes).
Learn how to migrate application workloads from VMs into Kubernetes by leveraging Consul and its L7 Traffic Management features. By establishing a common service mesh between both runtime platforms, we enable the ability to take a policy0driven approach to security and application communications.
In our previous blog we showed how to get started with deploying HashiCorp Consul Service (HCS) on Azure and joining it to an Azure Kubernetes Service (AKS) cluster. In the video above, we show how we can take Virtual Machines hosted in Microsoft Azure and bring them into the same Consul service mesh that our AKS cluster joined previously. This configuration currently requires connectivity between the Consul client nodes in the AKS and the Virtual Machine networks.