Skip to content
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

[release-1.9] Adding link to Event Mesh def page #5500

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
9 changes: 4 additions & 5 deletions docs/eventing/event-registry.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,8 +60,8 @@ EventType objects:

| Field | Description | Required or optional |
|-------|-------------|----------------------|
| `spec.type` | Refers to the [CloudEvent type](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#type) as it enters into the event mesh. Event consumers can create Triggers filtering on this attribute. This field is authoritative. | Required |
| `spec.source` | Refers to the [CloudEvent source](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#source-1) as it enters into the event mesh. Event consumers can create Triggers filtering on this attribute. | Required |
| `spec.type` | Refers to the [CloudEvent type](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#type) as it enters into the [event mesh](../event-mesh). Event consumers can create Triggers filtering on this attribute. This field is authoritative. | Required |
| `spec.source` | Refers to the [CloudEvent source](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#source-1) as it enters into the [event mesh](../event-mesh). Event consumers can create Triggers filtering on this attribute. | Required |
| `spec.schema` | A valid URI with the EventType schema such as a JSON schema or a protobuf schema. | Optional |
| `spec.description` | A string describing what the EventType is about. | Optional |
| `spec.broker` | Refers to the Broker that can provide the EventType. | Required |
Expand Down Expand Up @@ -150,8 +150,7 @@ two topics.

## Discover events using the registry

Using the registry, you can discover the different types of events that Broker
event meshes can consume.
Using the registry, you can discover the different types of events that [Broker event meshes](../event-mesh) can consume.

### View all event types you can subscribe to

Expand Down Expand Up @@ -195,7 +194,7 @@ For an example EventType YAML, see

## About subscribing to events

After you know what events can be consumed from the Brokers' event meshes,
After you know what events can be consumed from the Brokers' [event meshes](../event-mesh),
you can create Triggers to subscribe to particular events.

Here are a some example Triggers that subscribe to events using exact matching on
Expand Down
2 changes: 1 addition & 1 deletion docs/snippets/about-brokers.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,6 @@
- /docs/eventing/broker/README.md
-->

Brokers are Kubernetes custom resources that define an event mesh for collecting a pool of events. Brokers provide a discoverable endpoint for event ingress, and use Triggers for event delivery. Event producers can send events to a broker by POSTing the event.
Brokers are Kubernetes custom resources that define an [event mesh](/docs/eventing/event-mesh) for collecting a pool of events. Brokers provide a discoverable endpoint for event ingress, and use Triggers for event delivery. Event producers can send events to a broker by POSTing the event.

![Source 1 and Source 2 are transmitting some data -- ones and twos -- to the Broker, which then gets filtered by Triggers to the desired Sink.](https://user-images.githubusercontent.com/16281246/116248768-1fe56080-a73a-11eb-9a85-8bdccb82d16c.png){draggable=false}