From 8ba090199a8ddd09924ab6a8a12024a6c8e80a67 Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Sun, 16 Nov 2025 23:44:10 +0000 Subject: [PATCH 01/10] Modified event-mesh page --- docs/versioned/.nav.yml | 2 +- docs/versioned/eventing/{ => concepts}/event-mesh.md | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename docs/versioned/eventing/{ => concepts}/event-mesh.md (100%) diff --git a/docs/versioned/.nav.yml b/docs/versioned/.nav.yml index dafe945ba14..042f77701d5 100644 --- a/docs/versioned/.nav.yml +++ b/docs/versioned/.nav.yml @@ -119,7 +119,6 @@ nav: ############################################################################### - Eventing: - Knative Eventing overview: eventing/README.md - - Event Mesh: eventing/event-mesh.md - Concepts: - Brokers: - About Brokers: eventing/brokers/README.md @@ -132,6 +131,7 @@ nav: - RabbitMQ Broker: eventing/brokers/broker-types/rabbitmq-broker/README.md - Creating a Broker: eventing/brokers/create-broker.md - Developer configuration options: eventing/brokers/broker-developer-config-options.md + - Event Mesh: eventing/concepts/event-mesh.md - Triggers: - Using Triggers: eventing/triggers/README.md - Duck types: eventing/concepts/duck-typing.md diff --git a/docs/versioned/eventing/event-mesh.md b/docs/versioned/eventing/concepts/event-mesh.md similarity index 100% rename from docs/versioned/eventing/event-mesh.md rename to docs/versioned/eventing/concepts/event-mesh.md From 4fd74940fa35b04709ec5fd723ecae6a243b63f3 Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Sun, 16 Nov 2025 23:50:26 +0000 Subject: [PATCH 02/10] Moved release notes page --- docs/versioned/{reference => }/relnotes/README.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/versioned/{reference => }/relnotes/README.md (100%) diff --git a/docs/versioned/reference/relnotes/README.md b/docs/versioned/relnotes/README.md similarity index 100% rename from docs/versioned/reference/relnotes/README.md rename to docs/versioned/relnotes/README.md From cf38f02d40a698c5167a57771e00945fe6cbec62 Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Mon, 17 Nov 2025 00:03:49 +0000 Subject: [PATCH 03/10] Removed Eventing FAQ --- docs/versioned/eventing/faq/README.md | 13 ------------- 1 file changed, 13 deletions(-) delete mode 100644 docs/versioned/eventing/faq/README.md diff --git a/docs/versioned/eventing/faq/README.md b/docs/versioned/eventing/faq/README.md deleted file mode 100644 index d942bd4efa1..00000000000 --- a/docs/versioned/eventing/faq/README.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -audience: developer -components: - - eventing -function: reference ---- - -# Eventing FAQs - -## What is a Sugar Controller? - -The Sugar Controller is an optional controller which will automatically create and clean up brokers based on the creation/deletion of namespaces and triggers. -For more information on how to enable and configure the sugar controller, read the [sugar controller documentation](../sugar/README.md). From a81392f4e523c3f557a953ab9bfaa49e25fb7ecf Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Mon, 17 Nov 2025 00:06:03 +0000 Subject: [PATCH 04/10] Removed Eventing FAQ --- docs/versioned/.nav.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/versioned/.nav.yml b/docs/versioned/.nav.yml index 042f77701d5..d31f2d2791e 100644 --- a/docs/versioned/.nav.yml +++ b/docs/versioned/.nav.yml @@ -215,7 +215,6 @@ nav: - Observability: - Collecting metrics: eventing/observability/metrics/collecting-metrics.md - Metrics Reference: eventing/observability/metrics/eventing-metrics.md - - FAQ: eventing/faq/README.md # Eventing reference docs - Reference: - Eventing API: eventing/reference/eventing-api.md From 5cc779ad9ad89e84ed0d597789d6a6346bb32d58 Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Mon, 17 Nov 2025 00:23:53 +0000 Subject: [PATCH 05/10] Modified button label to Quick Start --- docs/versioned/.nav.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/versioned/.nav.yml b/docs/versioned/.nav.yml index d31f2d2791e..6b4d501639f 100644 --- a/docs/versioned/.nav.yml +++ b/docs/versioned/.nav.yml @@ -2,7 +2,7 @@ nav: ############################################################################### # Concepts ############################################################################### - - Overview: README.md + - Quick Start: README.md ############################################################################### # Getting started ############################################################################### From 2e83a574ef834c963646cb3b9d70d6b7e86ec24e Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Wed, 19 Nov 2025 20:48:53 +0000 Subject: [PATCH 06/10] Added redirects for event-mesh --- config/redirects.yml | 1 + docs/versioned/.nav.yml | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/config/redirects.yml b/config/redirects.yml index fffb48be1b5..0b55b253f04 100644 --- a/config/redirects.yml +++ b/config/redirects.yml @@ -226,3 +226,4 @@ plugins: versioned/serving/using-subroutes.md: versioned/serving/traffic-management.md versioned/eventing/brokers/create-mtbroker.md: versioned/eventing/brokers/create-broker.md versioned/eventing/brokers/broker-admin-config-options.md: versioned/eventing/configuration/broker-configuration.md + versioned/eventing/concepts/event-mesh.md: versioned/eventing/concepts/event-mesh.md diff --git a/docs/versioned/.nav.yml b/docs/versioned/.nav.yml index 6b4d501639f..03687dc5717 100644 --- a/docs/versioned/.nav.yml +++ b/docs/versioned/.nav.yml @@ -2,12 +2,12 @@ nav: ############################################################################### # Concepts ############################################################################### - - Quick Start: README.md + - Overview: README.md ############################################################################### # Getting started ############################################################################### - Tutorials: - - Overview: getting-started/tutorial.md + - Explore Knative: getting-started/tutorial.md - Quickstart: - Tutorial introduction: getting-started/README.md - Install Knative using quickstart: getting-started/quickstart-install.md From cda18fc3ba4c5420c6109b7b65cdd36f0f85410d Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Thu, 20 Nov 2025 20:07:58 +0000 Subject: [PATCH 07/10] Added FAQs and removed relnotes --- config/redirects.yml | 2 +- docs/versioned/.nav.yml | 1 + docs/versioned/eventing/faq/README.md | 13 +++++++++++++ docs/versioned/relnotes/README.md | 18 ------------------ 4 files changed, 15 insertions(+), 19 deletions(-) create mode 100644 docs/versioned/eventing/faq/README.md delete mode 100644 docs/versioned/relnotes/README.md diff --git a/config/redirects.yml b/config/redirects.yml index 0b55b253f04..4eebe62f8df 100644 --- a/config/redirects.yml +++ b/config/redirects.yml @@ -226,4 +226,4 @@ plugins: versioned/serving/using-subroutes.md: versioned/serving/traffic-management.md versioned/eventing/brokers/create-mtbroker.md: versioned/eventing/brokers/create-broker.md versioned/eventing/brokers/broker-admin-config-options.md: versioned/eventing/configuration/broker-configuration.md - versioned/eventing/concepts/event-mesh.md: versioned/eventing/concepts/event-mesh.md + versioned/eventing/event-mesh.md: versioned/eventing/concepts/event-mesh.md diff --git a/docs/versioned/.nav.yml b/docs/versioned/.nav.yml index 03687dc5717..92a47fe7121 100644 --- a/docs/versioned/.nav.yml +++ b/docs/versioned/.nav.yml @@ -215,6 +215,7 @@ nav: - Observability: - Collecting metrics: eventing/observability/metrics/collecting-metrics.md - Metrics Reference: eventing/observability/metrics/eventing-metrics.md + - FAQ: eventing/faq/README.md # Eventing reference docs - Reference: - Eventing API: eventing/reference/eventing-api.md diff --git a/docs/versioned/eventing/faq/README.md b/docs/versioned/eventing/faq/README.md new file mode 100644 index 00000000000..72cc7b3b06b --- /dev/null +++ b/docs/versioned/eventing/faq/README.md @@ -0,0 +1,13 @@ +--- +audience: developer +components: + - eventing +function: reference +--- + +# Eventing FAQs + +## What is a Sugar Controller? + +The Sugar Controller is an optional controller which will automatically create and clean up brokers based on the creation/deletion of namespaces and triggers. +For more information on how to enable and configure the sugar controller, read the [sugar controller documentation](/docs/eventing/sugar). diff --git a/docs/versioned/relnotes/README.md b/docs/versioned/relnotes/README.md deleted file mode 100644 index cd0f617dae5..00000000000 --- a/docs/versioned/relnotes/README.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -audience: developer -components: - - functions - - serving - - eventing -function: reference ---- - -# Knative release notes - -For details about the Knative releases, see the following pages: - -- [Knative CLI releases](https://github.com/knative/client/releases) -- [Knative Functions releases](https://github.com/knative/func/releases) -- [Knative Eventing releases](https://github.com/knative/eventing/releases) -- [Knative Serving releases](https://github.com/knative/serving/releases) -- [Knative Operator releases](https://github.com/knative/operator/releases) From 6579b057e4d53a5eb18bda41ed635d9ffab06ec1 Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Fri, 21 Nov 2025 00:25:59 +0000 Subject: [PATCH 08/10] Modified sugar controller documentation link --- docs/versioned/eventing/faq/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/versioned/eventing/faq/README.md b/docs/versioned/eventing/faq/README.md index 72cc7b3b06b..d942bd4efa1 100644 --- a/docs/versioned/eventing/faq/README.md +++ b/docs/versioned/eventing/faq/README.md @@ -10,4 +10,4 @@ function: reference ## What is a Sugar Controller? The Sugar Controller is an optional controller which will automatically create and clean up brokers based on the creation/deletion of namespaces and triggers. -For more information on how to enable and configure the sugar controller, read the [sugar controller documentation](/docs/eventing/sugar). +For more information on how to enable and configure the sugar controller, read the [sugar controller documentation](../sugar/README.md). From efbeaefb403fa05e0d76a8bcfd7ba6a70d5068ce Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Fri, 21 Nov 2025 17:43:59 +0000 Subject: [PATCH 09/10] Modified event-mesh page --- docs/versioned/eventing/brokers/README.md | 2 +- docs/versioned/eventing/concepts/event-mesh.md | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/versioned/eventing/brokers/README.md b/docs/versioned/eventing/brokers/README.md index bd82fa3f2bd..4a39fd40e25 100644 --- a/docs/versioned/eventing/brokers/README.md +++ b/docs/versioned/eventing/brokers/README.md @@ -7,7 +7,7 @@ function: explanation # Brokers -Brokers are Kubernetes custom resources that define an [event mesh](../event-mesh.md) 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](../concepts/event-mesh.md) 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} diff --git a/docs/versioned/eventing/concepts/event-mesh.md b/docs/versioned/eventing/concepts/event-mesh.md index b28175aedcb..026ed7b756b 100644 --- a/docs/versioned/eventing/concepts/event-mesh.md +++ b/docs/versioned/eventing/concepts/event-mesh.md @@ -13,13 +13,13 @@ In an Event Mesh, both producing and consuming applications do not need to imple ## Knative Event Mesh -The above mentioned _event brokers_ map directly to a core API in Knative Eventing: the [`Broker` API](../brokers) offers a discoverable endpoint for event ingress and the [`Trigger` API](../triggers) completes the offering with its event filtering and delivery capabilities. With these APIs Knative Eventing offers an Event Mesh as defined above: +The above mentioned _event brokers_ map directly to a core API in Knative Eventing: the [`Broker` API](../brokers) offers a discoverable endpoint for event ingress and the [`Trigger` API](../triggers/) completes the offering with its event filtering and delivery capabilities. With these APIs Knative Eventing offers an Event Mesh as defined above: -![Raw Trace](images/mesh.png) +![Raw Trace](../images/mesh.png) -As visible in the above diagram, the Event Mesh is defined with the `Broker` and `Trigger` APIs for the ingress and the egress of events. Knative Eventing enables multiple resources to participate in the Event Mesh with a partial schema pattern called "duck typing". Duck typing allows multiple resource types to advertise common capabilities, such as "can receive events at a URL" or "can deliver events to a destination". Knative Eventing uses these capabilities to offer [a pool of interoperable sources](../sources) for sending events to the `Broker` and [as destinations for `Trigger`-routed events](../triggers). The Knative Eventing APIs contain three categories of APIs: +As visible in the above diagram, the Event Mesh is defined with the `Broker` and `Trigger` APIs for the ingress and the egress of events. Knative Eventing enables multiple resources to participate in the Event Mesh with a partial schema pattern called "duck typing". Duck typing allows multiple resource types to advertise common capabilities, such as "can receive events at a URL" or "can deliver events to a destination". Knative Eventing uses these capabilities to offer [a pool of interoperable sources](../sources/) for sending events to the `Broker` and [as destinations for `Trigger`-routed events](../triggers/README.md). The Knative Eventing APIs contain three categories of APIs: -* **Events Ingress**: Support for connecting event senders: Source duck type and [SinkBinding](../custom-event-source/sinkbinding) to support easily configuring applications to deliver events to a `Broker`. Applications can submit events and use Eventing even without any sources installed. +* **Events Ingress**: Support for connecting event senders: Source duck type and [SinkBinding](../custom-event-source/sinkbinding/) to support easily configuring applications to deliver events to a `Broker`. Applications can submit events and use Eventing even without any sources installed. * **Event routing**: `Broker` and `Trigger` objects support defining the mesh and event routing. Note that `Broker` matches the definition of an Addressable event destination, so it is possible to relay events from a Broker in one cluster to a Broker in another cluster. Similarly, `Trigger` uses the same Deliverable duck type as many sources, so it is easy to substitute an event mesh for direct delivery of events. * **Event egress** : The Deliverable contract supports specifying either a bare URL or referencing a Kubernetes object which implements the Addressable interface (has a `status.address.url`) as a destination. All event destinations ("sinks") must implement the CloudEvents delivery specification, but do not necessarily need to implement any Kubernetes behavior -- a bare VM referenced by URL is an acceptable event egress. From 0769c23b69b7cc51063b5644212929c59985a2ce Mon Sep 17 00:00:00 2001 From: Mahendran Selvakumar Date: Fri, 21 Nov 2025 20:07:18 +0000 Subject: [PATCH 10/10] Modified event-mesh Page --- docs/versioned/eventing/concepts/event-mesh.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/versioned/eventing/concepts/event-mesh.md b/docs/versioned/eventing/concepts/event-mesh.md index 026ed7b756b..6223a85130d 100644 --- a/docs/versioned/eventing/concepts/event-mesh.md +++ b/docs/versioned/eventing/concepts/event-mesh.md @@ -13,13 +13,13 @@ In an Event Mesh, both producing and consuming applications do not need to imple ## Knative Event Mesh -The above mentioned _event brokers_ map directly to a core API in Knative Eventing: the [`Broker` API](../brokers) offers a discoverable endpoint for event ingress and the [`Trigger` API](../triggers/) completes the offering with its event filtering and delivery capabilities. With these APIs Knative Eventing offers an Event Mesh as defined above: +The above mentioned _event brokers_ map directly to a core API in Knative Eventing: the [`Broker` API](../brokers/README.md) offers a discoverable endpoint for event ingress and the [`Trigger` API](../triggers/README.md) completes the offering with its event filtering and delivery capabilities. With these APIs Knative Eventing offers an Event Mesh as defined above: ![Raw Trace](../images/mesh.png) -As visible in the above diagram, the Event Mesh is defined with the `Broker` and `Trigger` APIs for the ingress and the egress of events. Knative Eventing enables multiple resources to participate in the Event Mesh with a partial schema pattern called "duck typing". Duck typing allows multiple resource types to advertise common capabilities, such as "can receive events at a URL" or "can deliver events to a destination". Knative Eventing uses these capabilities to offer [a pool of interoperable sources](../sources/) for sending events to the `Broker` and [as destinations for `Trigger`-routed events](../triggers/README.md). The Knative Eventing APIs contain three categories of APIs: +As visible in the above diagram, the Event Mesh is defined with the `Broker` and `Trigger` APIs for the ingress and the egress of events. Knative Eventing enables multiple resources to participate in the Event Mesh with a partial schema pattern called "duck typing". Duck typing allows multiple resource types to advertise common capabilities, such as "can receive events at a URL" or "can deliver events to a destination". Knative Eventing uses these capabilities to offer [a pool of interoperable sources](../sources/README.md) for sending events to the `Broker` and [as destinations for `Trigger`-routed events](../triggers/README.md). The Knative Eventing APIs contain three categories of APIs: -* **Events Ingress**: Support for connecting event senders: Source duck type and [SinkBinding](../custom-event-source/sinkbinding/) to support easily configuring applications to deliver events to a `Broker`. Applications can submit events and use Eventing even without any sources installed. +* **Events Ingress**: Support for connecting event senders: Source duck type and [SinkBinding](../custom-event-source/sinkbinding/README.md) to support easily configuring applications to deliver events to a `Broker`. Applications can submit events and use Eventing even without any sources installed. * **Event routing**: `Broker` and `Trigger` objects support defining the mesh and event routing. Note that `Broker` matches the definition of an Addressable event destination, so it is possible to relay events from a Broker in one cluster to a Broker in another cluster. Similarly, `Trigger` uses the same Deliverable duck type as many sources, so it is easy to substitute an event mesh for direct delivery of events. * **Event egress** : The Deliverable contract supports specifying either a bare URL or referencing a Kubernetes object which implements the Addressable interface (has a `status.address.url`) as a destination. All event destinations ("sinks") must implement the CloudEvents delivery specification, but do not necessarily need to implement any Kubernetes behavior -- a bare VM referenced by URL is an acceptable event egress.