-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Add more information about Broker Developer Configuration Options #5993
Conversation
Welcome @0ZeKa0! It looks like this is your first PR to knative/docs 🎉 |
✅ Deploy Preview for knative ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @0ZeKa0,
thanks a lot for your work on this 👍
I left a few comments.
When I checked on your PR, I was thinking about merging the "Developer configuration options" and "Creating a Broker" page. Any objections on that? Otherwise we can continue with the split approach as in this PR to describe the needed options and then merge them later 🤷
@@ -1,6 +1,6 @@ | |||
# Developer configuration options | |||
|
|||
## Broker configuration example | |||
## Broker configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we move the full example to the end of the page. So we describe before the configuration options and give then a "full example"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving the full example would be better because a section from options was repeated on the Developer Configuration Options.
|
||
### Event Delivery Options | ||
- You can use `dead-letter sink` for error handling and auditing of undelivered messages. Specify Kubernetes object reference where undelivered messages will be sent using `ref` and an optional URI to route undelivered messages using `uri`. | ||
- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be `exponantial` or `linear`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be `exponantial` or `linear`. | |
- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be `exponantial` or `linear`. |
### Event Delivery Options | ||
- You can use `dead-letter sink` for error handling and auditing of undelivered messages. Specify Kubernetes object reference where undelivered messages will be sent using `ref` and an optional URI to route undelivered messages using `uri`. | ||
- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be `exponantial` or `linear`. | ||
- You can set the `Backoff delay ` to specify the initial delay before retrying, using the ISO 8601 duration format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- You can set the `Backoff delay ` to specify the initial delay before retrying, using the ISO 8601 duration format. | |
- You can set the `Backoff delay` to specify the initial delay before retrying, using the ISO 8601 duration format. |
- `spec.delivery` is used to configure event delivery options. Event delivery options specify what happens to an event that fails to be delivered to an event sink. For more information, see the documentation on [Event delivery](../event-delivery.md). | ||
|
||
### Advance broroker class options |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### Advance broroker class options | |
### Advanced Broker class options |
- `spec.delivery` is used to configure event delivery options. Event delivery options specify what happens to an event that fails to be delivered to an event sink. For more information, see the documentation on [Event delivery](../event-delivery.md). | ||
|
||
### Advance broroker class options | ||
When a Broker is created without a specified `eventing.knative.dev/broker.class` annotation, the default `MTChannelBasedBroker` Broker class is used, as specified by default in the `config-br-defaults` ConfigMap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a Broker is created without a specified `eventing.knative.dev/broker.class` annotation, the default `MTChannelBasedBroker` Broker class is used, as specified by default in the `config-br-defaults` ConfigMap. | |
When a Broker is created without a specified `eventing.knative.dev/broker.class` annotation, by default the `MTChannelBasedBroker` Broker class is used, as specified in the `config-br-defaults` ConfigMap. |
Thanks @0ZeKa0 ! |
|
||
### Event Delivery Options | ||
- You can use `dead-letter sink` for error handling and auditing of undelivered messages. Specify Kubernetes object reference where undelivered messages will be sent using `ref` and an optional URI to route undelivered messages using `uri`. | ||
- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be `exponantial` or `linear`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be `exponantial` or `linear`. | |
- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be `exponential` or `linear`. |
I thought that the expectation was merging just "Broker class options" section to "Developer Configuration Options" page. So let's continue with split approach. @creydr |
The full example moved to end of the page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one small nit. Looks LGTM otherwise
Co-authored-by: Christoph Stäbler <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @0ZeKa0 for fixing this 💪
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 0ZeKa0, Cali0707, creydr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
#5526