The HashiCorp Consul ecosystem continues its growth with the addition of 13 new Consul integrations.
The HashiCorp Consul ecosystem expanded with 13 new integrations, helping customers with improved observability, resilience, and security for their applications across any runtime platform and cloud. In March we also announced general availability for Consul 1.15 which simplifies user onboarding, enhances troubleshooting workflows, and reduces operational complexity.
In addition this quarter, HashiCorp completed a new Consul Deployment Guide on Google Kubernetes Engine (GKE).
Top IT industry players showed support for Consul with new integrations across our HCP Consul, Consul Enterprise, and Consul OSS solutions.
The HCP Consul integration with Circonus Observability monitors HCP Consul deployments with a plethora of Consul server, client, and Envoy metrics displayed via out-of-the-box dashboards built by Circonus.
Grafana Labs completed two integrations:
The HCP Consul observability integration with Grafana Cloud decreases service mesh downtime of HCP Consul environments streaming Consul and Envoy environment metrics to Grafana via Prometheus.
The Consul observability with Grafana Cloud integration which utilizes Grafana Cloud to monitor Consul and Envoy infrastructure, decreasing service disruption and mean-time-to-resolve (MTTR) via Grafana's Prometheus collector.
The HCP Consul integration with iLert leverages HCP Consul's own leadership election and K/V store to provide automatic failover and seamless operation in the case of a consul-alerts node failure and ensures that your notifications are still sent.
With both an HCP and Consul Enterprise integration with Netdata Cloud, Consul operators can now quickly build and maintain complex distributed systems while maintaining optimal uptime in Consul service discovery networks.
Operations personnel employing Neustar’s UltraDNS can now leverage Consul’s service catalog and two new UltraDNS Consul-Terraform-Sync modules for dynamically updating hosted DNS A, AAAA, and RD-Pool records as services within the Consul environment.
The Consul platform integration with SUSE Rancher has been completed with its certification of the Consul on Kubernetes Helm chart.
The HCP Consul observability integration with Splunk Cloud leverages Splunk's distribution of OpenTelemetry Collector to monitor HCP Consul environments, minimizing downtime and troubleshooting the cloud service meshes.
Zscaler completed three Consul Enterprise integrations:
The Consul-Terraform-Sync and Zscaler Private Access integration leverages the Zscaler Private Access Consul-Terraform-Sync module to create and update application segments dynamically in the ZPA Cloud.
The Consul-Terraform-Sync and Zscaler AppServer Automation integration leverages the Zscaler Private Access Consul-Terraform-Sync module to create and update application servers in the ZPA Cloud.
The Consul-Terraform-Sync and Zscaler Internet Access (ZIA) Cloud Firewall IP Source Group integration leverages the Zscaler Internet Access Consul-Terraform-Sync module to dynamically create and update IP source groups in the ZIA Cloud Firewall.
The HashiCorp Consul Integration Program allows our partners to integrate their products to work with Consul OSS, Enterprise, or HashiCorp Cloud Platform (HCP) Consul. Learn more at our Consul Integration Program page.
As a fully managed service, HCP Consul is the easiest way to deploy managed Consul in Amazon Web Services (AWS) or Microsoft Azure. For more information about HCP Consul and pricing, please visit the HCP product page or sign up through the HCP portal.
More information on earlier Consul integrations:
Use Minikube to create multiple Kubernetes clusters with Consul and test cluster peering configurations in your local development environment.
Consul 1.16 adds new reliability, scalability, security, service mesh UX, extensibility, and service discovery capabilities.
The HCP Consul management plane now offers deeper insights to your Consul deployments via cloud-based observability and seamlessly links new and existing self-managed Consul clusters.