From 3aa10720876753c48946bb550f9d867b495fb1e2 Mon Sep 17 00:00:00 2001 From: salaboy Date: Tue, 26 Aug 2025 08:21:10 +0100 Subject: [PATCH] Update README.md Signed-off-by: salaboy --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 82dfe1d..ce17c41 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ While sidecars are the default strategy, there are some use cases that require o Dapr Shared extends the Dapr sidecar model with two new deployment strategies: `DaemonSet` and `Deployment`. -No matter which strategy you choose, it is important to understand that in most use cases you will have one instance of Dapr Shared (Helm Release) per service (app-id). This means that if you have an application composed by three microservices, each service is recommended to have it's own Dapr Shared instance. Check the [step-by-step tutorial using Kubernetes KinD here](tutorial/README.md), to see an application using Dapr Shared. +No matter which strategy you choose, it is important to understand that in most use cases, you will have one instance of Dapr Shared (Helm Release) per service (app-id). This means that if you have an application composed of three microservices, each service is recommended to have its own Dapr Shared instance. Check the [step-by-step tutorial using Kubernetes KinD here](docs/tutorial/README.md), to see an application using Dapr Shared. ### Dapr Shared: DeamonSet strategy @@ -48,7 +48,7 @@ If you want to look at a step-by-step tutorial using some applications and inter ## From Source -To deploy this chart from the source you can run from inside the `chart/dapr-shared` directory: +To deploy this chart from the source, you can run from inside the `chart/dapr-shared` directory: ``` helm install my-shared . --set shared.appId= --set shared.remoteURL= --set shared.remotePort=