Skip to content

Commit 6d3a594

Browse files
fix eventing getting started doc (#4295)
1 parent 0bbc22f commit 6d3a594

File tree

1 file changed

+12
-8
lines changed

1 file changed

+12
-8
lines changed

docs/eventing/getting-started.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -21,17 +21,15 @@ kubectl create namespace event-example
2121

2222
The [broker](broker/README.md) allows you to route events to different event sinks or consumers.
2323

24-
1. Add a broker named `default` to your namespace by creating a YAML file using
25-
the following template:
24+
1. Add a broker named `default` to your namespace by copying the following YAML into a file:
2625

2726
```yaml
2827
apiVersion: eventing.knative.dev/v1
29-
kind: broker
28+
kind: Broker
3029
metadata:
3130
name: default
32-
namespace: <namespace>
31+
namespace: event-example
3332
```
34-
Where `<namespace>` is your namespace.
3533
3634
1. Apply the YAML file by running the command:
3735
@@ -43,9 +41,8 @@ the following template:
4341
1. Verify that the broker is working correctly, by entering the following command:
4442

4543
```bash
46-
kubectl -n <namespace> get broker default
44+
kubectl -n event-example get broker default
4745
```
48-
Where `<namespace>` is your namespace.
4946

5047
This shows information about your broker. If the broker is working correctly, it shows a `READY` status of `True`:
5148

@@ -69,6 +66,7 @@ demonstrate how you can configure your event producers to target a specific cons
6966
kind: Deployment
7067
metadata:
7168
name: hello-display
69+
namespace: event-example
7270
spec:
7371
replicas: 1
7472
selector:
@@ -88,6 +86,7 @@ demonstrate how you can configure your event producers to target a specific cons
8886
apiVersion: v1
8987
metadata:
9088
name: hello-display
89+
namespace: event-example
9190
spec:
9291
selector:
9392
app: hello-display
@@ -112,6 +111,7 @@ into a file:
112111
kind: Deployment
113112
metadata:
114113
name: goodbye-display
114+
namespace: event-example
115115
spec:
116116
replicas: 1
117117
selector:
@@ -132,6 +132,7 @@ into a file:
132132
apiVersion: v1
133133
metadata:
134134
name: goodbye-display
135+
namespace: event-example
135136
spec:
136137
selector:
137138
app: goodbye-display
@@ -173,6 +174,7 @@ Each trigger can specify a filter that enables selection of relevant events base
173174
kind: Trigger
174175
metadata:
175176
name: hello-display
177+
namespace: event-example
176178
spec:
177179
broker: default
178180
filter:
@@ -200,6 +202,7 @@ Each trigger can specify a filter that enables selection of relevant events base
200202
kind: Trigger
201203
metadata:
202204
name: goodbye-display
205+
namespace: event-example
203206
spec:
204207
broker: default
205208
filter:
@@ -253,6 +256,7 @@ The broker can only be accessed from within the cluster where Knative Eventing i
253256
labels:
254257
run: curl
255258
name: curl
259+
namespace: event-example
256260
spec:
257261
containers:
258262
# This could be any image that we can SSH into and has curl.
@@ -334,7 +338,7 @@ The broker can only be accessed from within the cluster where Knative Eventing i
334338
< Date: Mon, 12 Aug 2019 19:48:18 GMT
335339
```
336340
- To make the third request, which creates an event that has the `type`
337-
`greeting` and the`source` `sendoff`, run the following in the SSH terminal:
341+
`greeting` and the `source` `sendoff`, run the following in the SSH terminal:
338342
```bash
339343
curl -v "http://broker-ingress.knative-eventing.svc.cluster.local/event-example/default" \
340344
-X POST \

0 commit comments

Comments
 (0)