Introduction to HashiCorp Consul Service on Azure with AKS

As part of our release of HashiCorp Consul Service on Azure, we've released a set of HashiCorp Learn guides for HCS on Azure, as well as a video resource for helping deploy ACL's in Consul. It's highly encouraged to review these resources as you get started.

Are you a HashiCorp tools practitioner? Do you want to help shape the direction of HashiCorp Consul running in public cloud? HashiCorp Consul Service (HCS) on Azure is now available! To get started, take a look at the HCS on Azure learn guides or proceed directly to the Azure Marketplace:

The service will deploy Consul in a “secure by default” configuration within your Azure subscription, which can then be leveraged across your Azure environment for Kubernetes and VM-based workloads to:

• Register services and health checks using Consul’s service catalog against virtual machines and workloads running in Azure Kubernetes Service.
• Enable Service Discovery using Consul DNS.
• Secure communication across services with Consul Service Mesh. Practitioners can create Layer 7 traffic rules, as well as establish zero trust networking leveraging Consul Connect Intentions. For more information on this - take a look at our Learn guides for Consul Connect.
• Dynamically update service configurations using familiar tools like Consul-Template.

In the preview video below, we take you through the steps to get started quickly with HCS on Azure. You’ll see us navigate through the Azure Marketplace and request our HCS environment as well as provide some guidance around how to leverage the cluster after post-deployment.

Once our HCS cluster is successfully provisioned, we walk through taking an existing Azure Kubernetes Service (AKS) cluster, and joining it to the HCS environment. With these configurations in place - we’re able to deploy a Kubernetes-native application onto AKS and using Consul’s service mesh capabilities, configure a zero-trust security policy around the Kubernetes services.