namespace in all yaml samples

best-practices/troubleshooting/common_issues.md

@@ -14,6 +14,7 @@ apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: nodeapp
+  namespace: default
   labels:
     app: node
 spec:

best-practices/troubleshooting/tracing.md

@@ -30,6 +30,7 @@ apiVersion: dapr.io/v1alpha1
 kind: Configuration
 metadata:
   name: zipkin
+  namespace: default
 spec:
   tracing:
     enabled: true
@@ -74,11 +75,12 @@ For Standalone mode, create a Dapr configuration file locally and reference it w
 
 1. Create the following YAML file:
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Configuration
 metadata:
   name: zipkin
+  namespace: default
 spec:
   tracing:
     enabled: true

concepts/configuration/README.md

@@ -93,6 +93,7 @@ apiVersion: dapr.io/v1alpha1
 kind: Configuration
 metadata:
   name: myappconfig
+  namespace: default
 spec:
   tracing:
     enabled: true
@@ -121,11 +122,12 @@ workloadCertTTL  | string | Time a certificate is valid for. Default is 24 hours
 
 Example control plane configuration
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Configuration
 metadata:
   name: default
+  namespace: default
 spec:
   mtls:
     enabled: true

concepts/middleware/README.md

@@ -17,6 +17,7 @@ apiVersion: dapr.io/v1alpha1
 kind: Configuration
 metadata:
   name: pipeline
+  namespace: default
 spec:
   httpPipeline:
     handlers:

concepts/observability/logs.md

@@ -59,6 +59,7 @@ apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: pythonapp
+  namespace: default
   labels:
     app: python
 spec:

concepts/observability/traces.md

@@ -33,6 +33,7 @@ apiVersion: dapr.io/v1alpha1
 kind: Configuration
 metadata:
   name: tracing
+  namespace: default
 spec:
   tracing:
     enabled: true
@@ -49,6 +50,7 @@ apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: zipkin
+  namespace: default
 spec:
   type: exporters.zipkin
   metadata:

concepts/secrets/component-secrets.md

@@ -38,6 +38,7 @@ apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: statestore
+  namespace: default
 spec:
   type: state.redis
   metadata:
@@ -54,6 +55,7 @@ apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: statestore
+  namespace: default
 spec:
   type: state.redis
   metadata:
@@ -81,11 +83,12 @@ kubectl create secret generic eventhubs-secret --from-literal=connectionString=*
 
 Next, reference the secret in your binding:
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: eventhubs
+  namespace: default
 spec:
   type: bindings.azure.eventhubs
   metadata:

howto/setup-pub-sub-message-broker/setup-azure-servicebus.md

@@ -12,8 +12,8 @@ Create the following YAML file named `azuresb.yaml`:
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
-  namespace: <namespace>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: pubsub.azure.servicebus
   metadata:

howto/setup-state-store/setup-azure-cosmosdb.md

@@ -19,7 +19,7 @@ The next step is to create a Dapr component for CosmosDB.
 
 Create the following YAML file named `cosmos.yaml`:
 
-```
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:

howto/setup-state-store/setup-azure-tablestorage.md

@@ -18,7 +18,7 @@ The next step is to create a Dapr component for Azure Table Storage.
 
 Create the following YAML file named `azuretable.yaml`:
 
-```
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:

howto/setup-state-store/setup-cassandra.md

@@ -32,7 +32,7 @@ The next step is to create a Dapr component for Cassandra.
 
 Create the following YAML file named `cassandra.yaml`:
 
-```
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:

howto/setup-state-store/setup-cloudstate.md

@@ -21,7 +21,7 @@ The next step is to create a Dapr component for Cloudstate.
 
 Create the following YAML file named `cloudstate.yaml`:
 
-```
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:

howto/setup-state-store/setup-consul.md

@@ -31,7 +31,7 @@ The next step is to create a Dapr component for Consul.
 
 Create the following YAML file named `consul.yaml`:
 
-```
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:

howto/setup-state-store/setup-mongodb.md

@@ -35,7 +35,7 @@ The next step is to create a Dapr component for MongoDB.
 
 Create the following YAML file named `mongodb.yaml`:
 
-```
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:

howto/setup-state-store/setup-zookeeper.md

@@ -32,7 +32,7 @@ The next step is to create a Dapr component for Zookeeper.
 
 Create the following YAML file named `zookeeper.yaml`:
 
-```
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:

howto/trigger-app-with-input-binding/README.md

@@ -24,7 +24,7 @@ Create the following YAML file, named binding.yaml, and save this to the /compon
 
 *Note: When running in Kubernetes, apply this file to your cluster using `kubectl apply -f binding.yaml`*
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:

reference/api/bindings_api.md

@@ -15,11 +15,12 @@ Examples for bindings include ```Kafka```, ```Rabbit MQ```, ```Azure Event Hubs`
 
 A Dapr Binding yaml file has the following structure:
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.<TYPE>
   metadata:
@@ -54,6 +55,7 @@ apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: kafkaevent
+  namespace: default
 spec:
   type: bindings.kafka
   metadata:

reference/api/state_api.md

@@ -13,11 +13,12 @@
 
 A Dapr State Store component yaml file has the following structure:
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: state.<TYPE>
   metadata:
@@ -222,11 +223,12 @@ Actors don't support multiple state stores and require a transactional state sto
 To specify which state store to be used for actors, specify value of property `actorStateStore` as true in the metadata section of the state store component yaml file.
 Example: Following components yaml will configure redis to be used as the state store for Actors.
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: statestore
+  namespace: default
 spec:
   type: state.redis
   metadata:

reference/specs/bindings/blobstorage.md

@@ -1,10 +1,11 @@
 # Azure Blob Storage Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.azure.blobstorage
   metadata:

reference/specs/bindings/cosmosdb.md

@@ -1,10 +1,11 @@
 # Azure CosmosDB Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.azure.cosmosdb
   metadata:

reference/specs/bindings/dynamodb.md

@@ -1,10 +1,11 @@
 # AWS DynamoDB Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.aws.dynamodb
   metadata:

reference/specs/bindings/eventhubs.md

@@ -2,11 +2,12 @@
 
 See [this](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-dotnet-framework-getstarted-send) for instructions on how to set up an Event Hub.
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.azure.eventhubs
   metadata:

reference/specs/bindings/gcpbucket.md

@@ -1,10 +1,11 @@
 # GCP Storage Bucket Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.gcp.bucket
   metadata:

reference/specs/bindings/gcppubsub.md

@@ -1,10 +1,11 @@
 # GCP Cloud Pub/Sub Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.gcp.pubsub
   metadata:

reference/specs/bindings/http.md

@@ -1,10 +1,11 @@
 # HTTP Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.http
   metadata:

reference/specs/bindings/kafka.md

@@ -1,10 +1,11 @@
 # Kafka Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.kafka
   metadata:

reference/specs/bindings/kinesis.md

@@ -2,11 +2,12 @@
 
 See [this](https://aws.amazon.com/kinesis/data-streams/getting-started/) for instructions on how to set up an AWS Kinesis data streams
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.aws.kinesis
   metadata:

reference/specs/bindings/kubernetes.md

@@ -1,10 +1,11 @@
 # Kubernetes Events Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.kubernetes
   metadata:

reference/specs/bindings/mqtt.md

@@ -1,10 +1,11 @@
 # MQTT Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.mqtt
   metadata:

reference/specs/bindings/rabbitmq.md

@@ -1,10 +1,11 @@
 # RabbitMQ Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.rabbitmq
   metadata:

reference/specs/bindings/redis.md

@@ -1,10 +1,11 @@
 # Redis Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.redis
   metadata:

reference/specs/bindings/s3.md

@@ -1,10 +1,11 @@
 # AWS S3 Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.aws.s3
   metadata:

reference/specs/bindings/sendgrid.md

@@ -1,10 +1,11 @@
 # SendGrid Binding Spec
 
-```
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
   name: sendgrid
+  namespace: default
 spec:
   type: bindings.twilio.sendgrid
   metadata:

reference/specs/bindings/servicebusqueues.md

@@ -1,10 +1,11 @@
 # Azure Service Bus Queues Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.azure.servicebusqueues
   metadata:

reference/specs/bindings/signalr.md

@@ -4,7 +4,8 @@
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.azure.signalr
   metadata:

reference/specs/bindings/sns.md

@@ -1,10 +1,11 @@
 # AWS SNS Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.aws.sns
   metadata:

reference/specs/bindings/sqs.md

@@ -1,10 +1,11 @@
 # AWS SQS Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.aws.sqs
   metadata:

reference/specs/bindings/storagequeues.md

@@ -4,7 +4,8 @@
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.azure.storagequeues
   metadata:

reference/specs/bindings/twilio.md

@@ -1,10 +1,11 @@
 # Twilio SMS Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.twilio.sms
   metadata:

reference/specs/bindings/twitter.md

@@ -1,23 +1,24 @@
 # Kubernetes Events Binding Spec
 
-```yml
+```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
 metadata:
-  name: <name>
+  name: <NAME>
+  namespace: <NAMESPACE>
 spec:
   type: bindings.twitter
   metadata:
   - name: consumerKey
-    value: ''
+    value: ""
   - name: consumerSecret
-    value: ''
+    value: ""
   - name: accessToken
-    value: ''
+    value: ""
   - name: accessSecret
-    value: ''
+    value: ""
   - name: query
-    value: ''
+    value: ""
 ```