images for placement service

2019-10-27 17:01:47 -07:00 · 2019-10-27 17:01:47 -07:00 · 8a50ddb6a0
parent 9fa8cf007c
commit 8a50ddb6a0
5 changed files with 4 additions and 1 deletions
--- a/images/actors_id_hashing_calling.png
+++ b/images/actors_id_hashing_calling.png
--- a/images/actors_placement_service_registration.png
+++ b/images/actors_placement_service_registration.png
--- a/images/overview_kubernetes.png
+++ b/images/overview_kubernetes.png
--- a/images/overview_standalone.png
+++ b/images/overview_standalone.png
--- a/overview.md
+++ b/overview.md
@ -60,13 +60,16 @@ You can use the [Dapr CLI](https://github.com/dapr/cli) to run services locally.

 ![Dapr overview](images/overview_standalone.png)

+For more information on the actor *Placement* service see [actor overview](/concepts/actor/actor-overview.md#distribution-and-failover) 
+
 ## Running Dapr in Kubernetes mode 

 Dapr can be configured to run on any [Kubernetes cluster](https://github.com/dapr/samples/tree/master/2.hello-kubernetes). In Kubernetes the *dapr-sidecar-injector* and *dapr-operator* services provide first class integration to launch Dapr as a sidecar container in the same pod as the service and provides notifications of Dapr component updates provisioned into the cluster.
 
-
 ![Dapr overview](images/overview_kubernetes.png)

+For more information on the actor *Placement* service see [actor overview](/concepts/actor/actor-overview.md#distribution-and-failover) 
+
 In order to give your service an id and port known to Dapr and launch the Dapr sidecar container, you simply annotate your deployment like this.

      annotations: