HashiCorp Consul is coming to the Azure Marketplace as a managed service!
Are you a HashiCorp tools practitioner? Do you want to help shape the direction of HashiCorp Consul running in public cloud? We are currently enrolling customers in our HashiCorp Consul Service (HCS) on Azure private beta! You can sign up here.
Once registered and whitelisted by our SRE team, you can get started by navigating to the HashiCorp Consul Service on Azure tile in the Azure Marketplace.
This 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.
Signing up for the beta is easy, simply fill out the form here and we can help you get started!
Originally posted on Hashicorp Blog
Author: Cody De Arkland