From 6232d4cc5b5454a2c19d85f2cd1eef4fa04f635f Mon Sep 17 00:00:00 2001 From: Ori Zohar Date: Mon, 9 Aug 2021 15:39:56 -0700 Subject: [PATCH] Adding link to OSM from service mesh concept page --- daprdocs/content/en/concepts/service-mesh.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/daprdocs/content/en/concepts/service-mesh.md b/daprdocs/content/en/concepts/service-mesh.md index a5554515b..6110aa854 100644 --- a/daprdocs/content/en/concepts/service-mesh.md +++ b/daprdocs/content/en/concepts/service-mesh.md @@ -35,6 +35,8 @@ Watch these recordings from the Dapr community calls showing presentations on ru - General overview and a demo of [Dapr and Linkerd](https://youtu.be/xxU68ewRmz8?t=142) - Demo of running [Dapr and Istio](https://youtu.be/ngIDOQApx8g?t=335) +Also, learn more about [running Dapr with Open Service Mesh (OSM)]({{}}). + ## When to choose using Dapr, a service mesh, or both Should you be using Dapr, a service mesh, or both? The answer depends on your requirements. If, for example, you are looking to use Dapr for one or more building blocks such as state management or pub/sub, and you are considering using a service mesh just for network security or observability, you may find that Dapr is a good fit and that a service mesh is not required.