From f11a20fc1475533a00f1db0e5b5d8bdba1860cae Mon Sep 17 00:00:00 2001 From: Shubham Sharma Date: Mon, 4 Jul 2022 21:49:46 +0530 Subject: [PATCH] Clarify annotation format (#2579) Signed-off-by: Shubham Sharma Co-authored-by: Yaron Schneider --- .../operations/hosting/kubernetes/kubernetes-volume-mounts.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-volume-mounts.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-volume-mounts.md index d0b34c546..c6a47166b 100644 --- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-volume-mounts.md +++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-volume-mounts.md @@ -17,7 +17,9 @@ You can set the following annotations in your deployment YAML: 1. **dapr.io/volume-mounts**: for read-only volume mounts 1. **dapr.io/volume-mounts-rw**: for read-write volume mounts -These annotations are comma separated pairs of `volume:path`. Make sure that the corresponding Volumes exist in the Pod spec. +These annotations are comma separated pairs of `volume-name:path/in/container`. Make sure that the corresponding Volumes exist in the Pod spec. + +In the snippet below, `my-volume1` and `my-volume2` are available inside the sidecar container at `/tmp/sample1` and `/tmp/sample2` respectively, in read-only mode. `my-volume3` is available inside the sidecar container at `/tmp/sample3` in read-write mode. ```yaml apiVersion: apps/v1