Remove the duplicated install section, since Source/Channel are covered in the install guide (#2450)

Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
This commit is contained in:
Matthias Wessendorf 2020-05-25 18:18:47 +02:00 committed by GitHub
parent cc7bcdd410
commit 904b6bafa9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 48 deletions

View File

@ -2,24 +2,12 @@ You can install and configure the Apache Kafka CRD (`KafkaChannel`) as the defau
## Prerequisites
You must ensure that you meet the [prerequisites listed in the Apache Kafka overview](../README.md).
You must also have the following tools installed:
- `curl`
- `sed`
- Ensure that you meet the [prerequisites listed in the Apache Kafka overview](../README.md).
- A Kubernetes cluster with [Knative Kafka Channel installed](../../../../install/README.md).
## Creating a `KafkaChannel` channel CRD
Install the `KafkaChannel` sub-component on your Knative Eventing cluster:
```
curl -L "https://storage.googleapis.com/knative-releases/eventing-contrib/latest/kafka-channel.yaml" \
| sed 's/REPLACE_WITH_CLUSTER_URL/my-cluster-kafka-bootstrap.kafka:9092/' \
| kubectl apply --filename -
```
> Note: The above assumes that you have Apache Kafka installed in the `kafka`, as discussed [here](../README.md)!
Once the `KafkaChannel` API is available, create a new object by configuring the YAML file as follows:
Create a new object by configuring the YAML file as follows:
```
cat <<-EOF | kubectl apply -f -
@ -34,8 +22,6 @@ spec:
EOF
```
You can now set the `KafkaChannel` CRD as the default channel configuration.
## Specifying the default channel configuration
To configure the usage of the `KafkaChannel` CRD as the
@ -69,7 +55,7 @@ Now that `KafkaChannel` is set as the default channel configuration, you can use
```
cat <<-EOF | kubectl apply -f -
---
apiVersion: messaging.knative.dev/v1alpha1
apiVersion: messaging.knative.dev/v1beta1
kind: Channel
metadata:
name: testchannel-one
@ -126,7 +112,7 @@ To use the Apache Kafka based broker, let's take a look at a simple demo. Use th
```
2. Install a source that publishes to the default broker
```
kubectl apply --filename 020-k8s-events.yaml
kubectl apply -f 020-k8s-events.yaml
```
3. Create a trigger that routes the events to the `ksvc`:

View File

@ -2,33 +2,10 @@ Tutorial on how to build and deploy a `KafkaSource` [Eventing source](../../../s
## Prerequisites
You must ensure that you meet the [prerequisites listed in the Apache Kafka overview](../README.md).
- Ensure that you meet the [prerequisites listed in the Apache Kafka overview](../README.md).
- A Kubernetes cluster with [Knative Kafka Source installed](../../../../install/README.md).
## Creating a `KafkaSource` source CRD
1. Install the `KafkaSource` sub-component to your Knative cluster:
```
kubectl apply -f https://storage.googleapis.com/knative-releases/eventing-contrib/latest/kafka-source.yaml
```
2. Check that the `kafka-controller-manager-0` pod is running.
```
kubectl get pods --namespace knative-sources
NAME READY STATUS RESTARTS AGE
kafka-controller-manager-0 1/1 Running 0 42m
```
3. Check the `kafka-controller-manager-0` pod logs.
```
$ kubectl logs kafka-controller-manager-0 -n knative-sources
2019/03/19 22:25:54 Registering Components.
2019/03/19 22:25:54 Setting up Controller.
2019/03/19 22:25:54 Adding the Apache Kafka Source controller.
2019/03/19 22:25:54 Starting Apache Kafka controller.
```
### Apache Kafka Topic (Optional)
## Apache Kafka Topic (Optional)
1. If using Strimzi, you can set a topic modifying `source/kafka-topic.yaml`
with your desired:
@ -69,7 +46,7 @@ You must ensure that you meet the [prerequisites listed in the Apache Kafka over
knative-demo-topic 16s
```
### Create the Event Display service
## Create the Event Display service
1. Download a copy of the code:
@ -112,7 +89,7 @@ You must ensure that you meet the [prerequisites listed in the Apache Kafka over
...
```
#### Apache Kafka Event Source
### Apache Kafka Event Source
1. Modify `source/event-source.yaml` accordingly with bootstrap servers, topics,
etc...:
@ -322,4 +299,3 @@ KafkaSource expects these files to be in pem format, if it is in other format li
kind: Service
name: event-display
```