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

Adding a bit more of clarfication on default channel configs (#3433) 

* Adding a bit more of clarfication on default channel config, and how to change the channel impl of the ootb broker

Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>

* Update docs/install/operator/configuring-eventing-cr.md

Co-authored-by: Omer B. <obensaadon@vmware.com>

* Update docs/install/operator/configuring-eventing-cr.md

Co-authored-by: Omer B. <obensaadon@vmware.com>

* Update docs/install/operator/configuring-eventing-cr.md

Co-authored-by: Omer B. <obensaadon@vmware.com>

* Update docs/install/operator/configuring-eventing-cr.md

Co-authored-by: Omer B. <obensaadon@vmware.com>

* Update docs/install/operator/configuring-eventing-cr.md

* Update docs/install/operator/configuring-eventing-cr.md

Co-authored-by: Ashleigh Brennan <abrennan@redhat.com>
Co-authored-by: Omer B. <obensaadon@vmware.com>
This commit is contained in:
Matthias Wessendorf 2021-04-08 15:03:50 +02:00 committed by GitHub
parent 97b375dbee
commit acb2937d92
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 27 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
docs/install/operator/configuring-eventing-cr.md
View File

@ -46,9 +46,11 @@ All Knative Eventing ConfigMaps are created in the same namespace as the Knative
Knative Eventing has multiple ConfigMaps that are named with the prefix `config-`.
The `spec.config` in the KnativeEventing CR has one `<name>` entry for each ConfigMap, named `config-<name>`, with a value which will be used for the ConfigMap `data`.
### Setting the default channel for the broker
### Setting a default channel
If you are using a channel-based broker, you can change the default channel type for the broker from InMemoryChannel to KafkaChannel, by updating the `config-br-default-channel` ConfigMap. You can do this by modifying the KnativeEventing CR:
If you are using different channel implementations, like the KafkaChannel, or you want a specific configuration of the InMemoryChannel to be the default configuration, you can change the default behavior by updating the `default-ch-webhook` ConfigMap.
You can do this by modifying the KnativeEventing CR:
```yaml
apiVersion: operator.knative.dev/v1alpha1
@ -79,6 +81,29 @@ spec:
**NOTE:** The `clusterDefault` setting determines the global, cluster-wide default channel type. You can configure channel defaults for individual namespaces by using the `namespaceDefaults` setting.
### Setting the default channel for the broker
If you are using a channel-based broker, you can change the default channel type for the broker from InMemoryChannel to KafkaChannel, by updating the `config-br-default-channel` ConfigMap.
You can do this by modifying the KnativeEventing CR:
```yaml
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeEventing
metadata:
name: knative-eventing
namespace: knative-eventing
spec:
config:
config-br-default-channel:
channelTemplateSpec: |
apiVersion: messaging.knative.dev/v1beta1
kind: KafkaChannel
spec:
numPartitions: 6
replicationFactor: 1
```
## Private repository and private secrets
The Knative Eventing Operator CR is configured the same way as the Knative Serving Operator CR.