Skip to content

Format markdown #1051

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
knative-prow-robot merged 1 commit into from
Apr 14, 2019
Merged

Format markdown #1051

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 19 additions & 5 deletions docs/broker/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,24 +53,38 @@ spec:

### ClusterChannelProvisioner

`Broker`'s use their `spec.channelTemplate` to create their internal `Channel`s, which dictate the durability guarantees of events sent to that `Broker`. If `spec.channelTemplate` is not specified, then the [default provisioner](https://www.knative.dev/docs/eventing/channels/default-channels/) for their namespace is used.
`Broker`'s use their `spec.channelTemplate` to create their internal `Channel`s,
which dictate the durability guarantees of events sent to that `Broker`. If
`spec.channelTemplate` is not specified, then the
[default provisioner](https://www.knative.dev/docs/eventing/channels/default-channels/)
for their namespace is used.

#### Setup

Have a `ClusterChannelProvisioner` installed and set as the [default provisioner](https://www.knative.dev/docs/eventing/channels/default-channels/) for the namespace you are interested in. For development, the [`in-memory` `ClusterChannelProvisioner`](https://github.com/knative/eventing/tree/master/config/provisioners/in-memory-channel#deployment-steps) is normally used.
Have a `ClusterChannelProvisioner` installed and set as the
[default provisioner](https://www.knative.dev/docs/eventing/channels/default-channels/)
for the namespace you are interested in. For development, the
[`in-memory` `ClusterChannelProvisioner`](https://github.com/knative/eventing/tree/master/config/provisioners/in-memory-channel#deployment-steps)
is normally used.

#### Changing

**Note** changing the `ClusterChannelProvisioner` of a running `Broker` will lose all in-flight events.
**Note** changing the `ClusterChannelProvisioner` of a running `Broker` will
lose all in-flight events.

If you want to change which `ClusterChannelProvisioner` is used by a given `Broker`, then determine if the `spec.channelTemplate` is specified or not.
If you want to change which `ClusterChannelProvisioner` is used by a given
`Broker`, then determine if the `spec.channelTemplate` is specified or not.

If `spec.channelTemplate` is specified:

1. Delete the `Broker`.
1. Create the `Broker` with the updated `spec.channelTemplate`.

If `spec.channelTemplate` is not specified:
1. Change the [default provisioner](https://github.com/knative/docs/blob/master/docs/eventing/channels/default-channels.md#setting-the-default-channel-configuration) for the namespace that `Broker` is in.

1. Change the
[default provisioner](https://github.com/knative/docs/blob/master/docs/eventing/channels/default-channels.md#setting-the-default-channel-configuration)
for the namespace that `Broker` is in.
1. Delete and recreate the `Broker`.

### Broker
Expand Down