From 391299aaa5468c3d13cb7cca8fe416f583660be5 Mon Sep 17 00:00:00 2001 From: Stepan Date: Wed, 6 Oct 2021 23:31:49 +0300 Subject: [PATCH] Adding 'dapr.io/sidecar-listen-addresses' annotation to middleware quickstart (#479) * middleware: adding dapr.io/sidecar-listen-addresses annotation to echoapp deployment and note to readme * changes after review; adding link to annotation details in the new note --- middleware/README.md | 2 ++ middleware/deploy/echoapp.yaml | 1 + 2 files changed, 3 insertions(+) diff --git a/middleware/README.md b/middleware/README.md index b31458da7..1da62a5b0 100644 --- a/middleware/README.md +++ b/middleware/README.md @@ -78,6 +78,8 @@ kubectl apply -f deploy/pipeline.yaml Next, you'll deploy the application and define an ingress rule that routes to the ```-dapr``` service that gets automatically created when you deploy your pod. In this case, all traffic is routed to the Dapr sidecar, which can reinforce various policies through middleware. +>**Note:** 'dapr.io/sidecar-listen-addresses' annotation is added to echoapp deployment to allow external connections. Be cautious of using it in a production environment. To read more on this annotation see [Dapr arguments and annotations for daprd, CLI, and Kubernetes](https://docs.dapr.io/reference/arguments-annotations-overview/) + 1. Deploy the application and the ingress rule: ```bash diff --git a/middleware/deploy/echoapp.yaml b/middleware/deploy/echoapp.yaml index 8c2a63cdf..e87f9de73 100644 --- a/middleware/deploy/echoapp.yaml +++ b/middleware/deploy/echoapp.yaml @@ -18,6 +18,7 @@ spec: dapr.io/app-id: "echoapp" dapr.io/app-port: "3000" dapr.io/config: "pipeline" + dapr.io/sidecar-listen-addresses: "0.0.0.0" spec: containers: - name: echo