Fix inaccurate description of `default-br-config` (#4182)

* Fix inaccurate description of `default-br-config`

* (review) Apply requested changes
This commit is contained in:
Antoine Cotten 2021-09-06 16:01:43 +02:00 committed by GitHub
parent a07d7cfc18
commit e9080d83e2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 9 deletions

View File

@ -13,7 +13,7 @@ metadata:
labels:
eventing.knative.dev/release: devel
data:
# Configuration for defaulting Channels that do not specify CRD implementations.
# Configures the default for any Broker that does not specify a spec.config or Broker class.
default-br-config: |
clusterDefault:
brokerClass: MTChannelBasedBroker
@ -56,7 +56,7 @@ metadata:
labels:
eventing.knative.dev/release: devel
data:
# Configuration for defaulting Channels that do not specify CRD implementations.
# Configures the default for any Broker that does not specify a spec.config or Broker class.
default-br-config: |
clusterDefault:
brokerClass: MTChannelBasedBroker
@ -86,7 +86,7 @@ metadata:
labels:
eventing.knative.dev/release: devel
data:
# Configuration for defaulting Channels that do not specify CRD implementations.
# Configures the default for any Broker that does not specify a spec.config or Broker class.
default-br-config: |
clusterDefault:
brokerClass: MTChannelBasedBroker
@ -170,7 +170,7 @@ the backing Channel for the Broker class:
```
### Configuring the default BrokerClass for the cluster
You can configure the `clusterDefault` Broker class so that any Broker created in the cluster that does not have a `BrokerClass` annotation uses this default class.
#### Example
@ -184,18 +184,18 @@ metadata:
labels:
eventing.knative.dev/release: devel
data:
# Configuration for defaulting Channels that do not specify CRD implementations.
# Configures the default for any Broker that does not specify a spec.config or Broker class.
default-br-config: |
clusterDefault:
brokerClass: MTChannelBasedBroker
```
### Configuring the default BrokerClass for namespaces
You can modify the default Broker class for one or more namespaces.
For example, if you want to use a `KafkaBroker` class for all other Brokers created on the cluster, but you want to use the `MTChannelBasedBroker` class for Brokers created in `namespace-1` and `namespace-2`, you would use the following ConfigMap settings:
```yaml
apiVersion: v1
kind: ConfigMap
@ -205,7 +205,7 @@ metadata:
labels:
eventing.knative.dev/release: devel
data:
# Configuration for defaulting Channels that do not specify CRD implementations.
# Configures the default for any Broker that does not specify a spec.config or Broker class.
default-br-config: |
clusterDefault:
brokerClass: KafkaBroker