knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove redundant (and errorneous) installation of eventing-sources (#536) 

* Remove redundant (and errorneous) installation of eventing-sources

* Remove other extraneous cruft (eventing sources, move channel to its own section
This commit is contained in:
Ville Aikas 2018-11-12 15:07:45 -08:00 committed by Knative Prow Robot
parent 1ca885c75c
commit 7d72822372
1 changed files with 4 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
eventing/samples/kubernetes-event-source/README.md
View File

@ -8,9 +8,10 @@ consumption by a function that has been implemented as a Knative Service.
### Prerequisites
1. Setup [Knative Eventing](https://github.com/knative/docs/tree/master/eventing).
1. Install [Knative Eventing Sources](https://github.com/knative/docs/tree/master/eventing-sources).
1. Install the [in-memory `ClusterChannelProvisioner`](https://github.com/knative/eventing/tree/master/config/provisioners/in-memory-channel).
- Note that you can skip this if you choose to use a different type of `Channel`. If so, you will need to modify `channel.yaml` before deploying it.
### Channel
1. Create a `Channel`. You can use your own `Channel` or use the provided sample, which creates a channel called `testchannel`. If you use your own `Channel` with a different name, then you will need to alter other commands later.
```shell
@ -25,16 +26,6 @@ kubectl -n default apply -f eventing/samples/kubernetes-event-source/channel.yam
kubectl apply -f eventing/samples/kubernetes-event-source/serviceaccount.yaml
```
### Deploy Event Sources
1. Deploy the `KubernetesEventSource` controller as part of eventing-source's controller. This makes kubernetes events available for subscriptions.
```shell
ko apply -f config/default.yaml
```
### Create Event Source for Kubernetes Events
1. In order to receive events, you have to create a concrete Event Source for a specific namespace. If you are wanting to consume events from a differenet namespace or using a different `Service Account`, you need to modify the yaml accordingly.