Add other services

daprdocs/content/en/concepts/dapr-services/placement.md

@@ -0,0 +1,16 @@
+---
+type: docs
+title: "Dapr placement service overview"
+linkTitle: "Placement"
+description: "Overview of the Dapr placement process"
+---
+
+The Dapr placement service is used to calculate and distribute distributed hash tables for the location of [Dapr actors]({{< ref actors >}} running in [self-hosted mode]({{< ref self-hosted >}}) or on [Kubernetes]({{< ref kubernetes >}}). This hash table maps actor IDs to pods or processes so a Dapr application can communicate with the actor.Anytime a Dapr application activates a Dapr actor, the placement updates the hash tables with the latest actor locations.
+
+## Self-hosted mode
+
+The placement service Docker container is started automatically as part of [`dapr init`]({{< ref self-hosted-with-docker.md >}}). It can also be run manually as a process if you are running in [slim-init mode]({{< ref self-hosted-no-docker.md >}}).
+
+## Kubernetes mode
+
+The placement service is deployed as part of `dapr init -k`, or via the Dapr Helm charts. For more information on running Dapr on Kubernetes, visit the [Kubernetes hosting page]({{< ref kubernetes >}}).

daprdocs/content/en/concepts/dapr-services/sentry.md

@@ -0,0 +1,26 @@
+---
+type: docs
+title: "Dapr sentry service overview"
+linkTitle: "Sentry"
+description: "Overview of the Dapr sentry process"
+---
+
+The Dapr sentry service manages mTLS between services and acts as a certificate authority. It generates mTLS certificates and distributes them to any running sidecars. This allows sidecars to communicate with encrypted, mTLS traffic. For more information read the [sidecar-to-sidecar communication overview]({{< ref "security-concept.md#sidecar-to-sidecar-communication" >}}). 
+
+## Self-hosted mode
+
+The sentry service Docker container is started automatically as part of [`dapr init`]({{< ref self-hosted-with-docker.md >}}). It can also be run manually as a process if you are running in [slim-init mode]({{< ref self-hosted-no-docker.md >}}).
+
+<img src="/images/security-mTLS-sentry-selfhosted.png" width=1000>
+
+## Kubernetes mode
+
+The sentry service is deployed as part of `dapr init -k`, or via the Dapr Helm charts. For more information on running Dapr on Kubernetes, visit the [Kubernetes hosting page]({{< ref kubernetes >}}).
+
+<img src="/images/security-mTLS-sentry-kubernetes.png" width=1000>
+
+## Further reading
+
+- [Security overview]({{< ref security-concept.md >}})
+- [Self-hosted mode]({{< ref self-hosted-with-docker.md >}})
+- [Kubernetes mode]({{< ref kubernetes >}})

daprdocs/content/en/concepts/dapr-services/sidecar-injector.md

@@ -0,0 +1,12 @@
+---
+type: docs
+title: "Dapr sidecar injector overview"
+linkTitle: "Sidecar"
+description: "Overview of the Dapr sidecar injector process"
+---
+
+When running Dapr in [Kubernetes mode]({{< ref kubernetes >}}), a pod is created running the dapr-sidecar-injector service, which looks for pods initialized with the [Dapr annotations]({{< ref arguments-annotations-overview.md >}}), and then creates another container in that pod for the [daprd service]({{< ref sidecar >}})
+
+## Running the sidecar injector
+
+The sidecar injector service is deployed as part of `dapr init -k`, or via the Dapr Helm charts. For more information on running Dapr on Kubernetes, visit the [Kubernetes hosting page]({{< ref kubernetes >}}).

daprdocs/content/en/concepts/dapr-services/sidecar.md

@@ -2,7 +2,7 @@
 type: docs
 title: "Dapr sidecar (daprd) overview"
 linkTitle: "Sidecar"
-weight: 300
+weight: 100
 description: "Overview of the Dapr sidecar process"
 ---