From ae6d065260d8ebffb0e995891eedda4c0b84fba8 Mon Sep 17 00:00:00 2001 From: Yaron Schneider Date: Thu, 10 Oct 2024 12:02:57 -0700 Subject: [PATCH] fix misleading wording (#4379) Signed-off-by: yaron2 --- daprdocs/content/en/concepts/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/concepts/overview.md b/daprdocs/content/en/concepts/overview.md index 106a772e5c4..ff0f7ad3114 100644 --- a/daprdocs/content/en/concepts/overview.md +++ b/daprdocs/content/en/concepts/overview.md @@ -108,7 +108,7 @@ Deploying and running a Dapr-enabled application into your Kubernetes cluster is ### Clusters of physical or virtual machines -The Dapr control plane services can be deployed in high availability (HA) mode to clusters of physical or virtual machines in production. In the diagram below, the Actor `Placement` and security `Sentry` services are started on three different VMs to provide HA control plane. In order to provide name resolution using DNS for the applications running in the cluster, Dapr uses [Hashicorp Consul service]({{< ref setup-nr-consul >}}), also running in HA mode. +The Dapr control plane services can be deployed in high availability (HA) mode to clusters of physical or virtual machines in production. In the diagram below, the Actor `Placement` and security `Sentry` services are started on three different VMs to provide HA control plane. In order to provide name resolution using DNS for the applications running in the cluster, Dapr uses multicast DNS by default, but can also optionally support [Hashicorp Consul service]({{< ref setup-nr-consul >}}). Architecture diagram of Dapr control plane and Consul deployed to VMs in high availability mode