ADDED VERBIAGE/REFERENCES TO BROKER CREATION

Some environments may not have Broker Injection in place. This commit adds a Note to the steps that perform Broker Injection, pointing to a previously created Broker page with instructions on how to create the broker by hand.
meteatamel · Aug 2, 2020 · 568f5de · 568f5de
1 parent 0da6e68
commit 568f5de
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 0 deletions.
diff --git a/docs/brokertrigger.md b/docs/brokertrigger.md
@@ -40,6 +40,8 @@ NAME
 inmemorychannel.messaging.knative.dev/default-kne-trigger
 ```
 
+*Note:* If your environment doesn't support automatic injection, refer to [Broker](broker.md).
+
 ## Source
 
 Create a `PingSource` to target the Broker. Define [source.yaml](../eventing/brokertrigger/source.yaml).

diff --git a/docs/eventregistry.md b/docs/eventregistry.md
@@ -27,6 +27,8 @@ NAME      READY   REASON   URL
 default   True             http://default-broker.default.svc.cluster.local
 ```
 
+*Note:* If your environment doesn't support automatic injection, refer to [Broker](broker.md).
+
 Now, create a CronJob event source. You can use the [cronjob-source-broker.yaml](../eventing/cronjob/cronjob-source-broker.yaml) from [ScheduledEventing](scheduledeventing.md).
 
 ```bash

diff --git a/docs/scheduledeventing.md b/docs/scheduledeventing.md
@@ -47,6 +47,8 @@ NAME      READY   REASON   URL
 default   True             http://broker-ingress.knative-eventing.svc.cluster.local/default/default
 ```
 
+*Note:* If your environment doesn't support automatic injection, refer to [Broker](broker.md).
+
 ## Event source - Broker sink
 
 Next, setup `PingSource` to point to our Broker instead.