mirror of https://github.com/knative/docs.git
[Kafka Broker] Change installation steps and artifact names (#2815)
The control plane is now a separate artifact, so we need to add another step to the installation and rename the control plane and the logging config artifacts. - Renamed `kafka-broker-config-logging` -> `kafka-config-logging` - Renamed `kafka-broker-controller` -> `kafka-controller` Signed-off-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
This commit is contained in:
parent
3483924ff9
commit
e274ef04ae
|
@ -22,13 +22,19 @@ Notable features are:
|
|||
|
||||
## Installation
|
||||
|
||||
1. Install the Kafka broker by entering the following command:
|
||||
1. Install the Kafka controller by entering the following command:
|
||||
|
||||
```bash
|
||||
kubectl apply --filename {{< artifact org="knative-sandbox" repo="eventing-kafka-broker" file="eventing-kafka-controller.yaml" >}}
|
||||
```
|
||||
|
||||
1. Install the Kafka Broker data plane by entering the following command:
|
||||
|
||||
```bash
|
||||
kubectl apply --filename {{< artifact org="knative-sandbox" repo="eventing-kafka-broker" file="eventing-kafka-broker.yaml" >}}
|
||||
```
|
||||
|
||||
2. Verify that `kafka-broker-controller`, `kafka-broker-receiver` and `kafka-broker-dispatcher` are running,
|
||||
2. Verify that `kafka-controller`, `kafka-broker-receiver` and `kafka-broker-dispatcher` are running,
|
||||
by entering the following command:
|
||||
|
||||
```bash
|
||||
|
@ -41,7 +47,7 @@ by entering the following command:
|
|||
NAME READY UP-TO-DATE AVAILABLE AGE
|
||||
eventing-controller 1/1 1 1 10s
|
||||
eventing-webhook 1/1 1 1 9s
|
||||
kafka-broker-controller 1/1 1 1 3s
|
||||
kafka-controller 1/1 1 1 3s
|
||||
kafka-broker-dispatcher 1/1 1 1 4s
|
||||
kafka-broker-receiver 1/1 1 1 5s
|
||||
```
|
||||
|
@ -158,7 +164,7 @@ installation step:
|
|||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: kafka-broker-config-logging
|
||||
name: kafka-config-logging
|
||||
namespace: knative-eventing
|
||||
data:
|
||||
config.xml: |
|
||||
|
@ -174,14 +180,14 @@ data:
|
|||
|
||||
To change the logging level to `DEBUG`, you need to:
|
||||
|
||||
1. Apply the following `kafka-broker-config-logging` `ConfigMap` or replace `level="INFO"` with `level="DEBUG"` to the
|
||||
`ConfigMap` `kafka-broker-config-logging`:
|
||||
1. Apply the following `kafka-config-logging` `ConfigMap` or replace `level="INFO"` with `level="DEBUG"` to the
|
||||
`ConfigMap` `kafka-config-logging`:
|
||||
|
||||
```yaml
|
||||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: kafka-broker-config-logging
|
||||
name: kafka-config-logging
|
||||
namespace: knative-eventing
|
||||
data:
|
||||
config.xml: |
|
||||
|
|
|
@ -608,12 +608,21 @@ kubectl apply --filename {{< artifact repo="eventing" file="in-memory-channel.ya
|
|||
{{< tabs name="eventing_brokers" default="MT-Channel-based" >}}
|
||||
{{% tab name="Apache Kafka Broker" %}}
|
||||
{{< feature-state version="v0.17" state="alpha" >}}
|
||||
The following command installs the Apache Kafka broker, and runs event routing in a system namespace,
|
||||
|
||||
The following commands install the Apache Kafka broker, and run event routing in a system namespace,
|
||||
`knative-eventing`, by default.
|
||||
|
||||
```bash
|
||||
kubectl apply --filename {{< artifact org="knative-sandbox" repo="eventing-kafka-broker" file="eventing-kafka-broker.yaml" >}}
|
||||
```
|
||||
1. Install the Kafka controller by entering the following command:
|
||||
|
||||
```bash
|
||||
kubectl apply --filename {{< artifact org="knative-sandbox" repo="eventing-kafka-broker" file="eventing-kafka-controller.yaml" >}}
|
||||
```
|
||||
|
||||
1. Install the Kafka Broker data plane by entering the following command:
|
||||
|
||||
```bash
|
||||
kubectl apply --filename {{< artifact org="knative-sandbox" repo="eventing-kafka-broker" file="eventing-kafka-broker.yaml" >}}
|
||||
```
|
||||
|
||||
For more information, see the [Kafka Broker](./../eventing/broker/kafka-broker.md) documentation.
|
||||
{{< /tab >}}
|
||||
|
|
Loading…
Reference in New Issue