drop eventing-rabbitmq (#5861)

config/nav.yml

@@ -195,7 +195,6 @@ nav:
             - Apache Kafka: 
               - About Apache Kafka Broker: eventing/brokers/broker-types/kafka-broker/README.md
               - Configuring Kafka features: eventing/brokers/broker-types/kafka-broker/configuring-kafka-features.md
-            - 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
         - Triggers:
@@ -215,7 +214,6 @@ nav:
           - PingSource:
             - Creating a PingSource object: eventing/sources/ping-source/README.md
             - PingSource reference: eventing/sources/ping-source/reference.md
-          - RabbitMQSource: eventing/sources/rabbitmq-source/README.md
           - RedisStreamSource:
             - About RedisStreamSource: eventing/sources/redis/README.md
             - Creating a RedisStreamSource object: eventing/sources/redis/getting-started.md

config/redirects.yml

@@ -6,7 +6,6 @@ plugins:
       eventing/broker/create-mtbroker.md: eventing/brokers/create-broker.md
       eventing/broker/example-mtbroker.md: eventing/brokers/broker-developer-config-options.md
       eventing/broker/kafka-broker/README.md: eventing/brokers/broker-types/kafka-broker/README.md
-      eventing/broker/rabbitmq-broker/README.md: eventing/brokers/broker-types/rabbitmq-broker/README.md
       eventing/broker/README.md: eventing/brokers/README.md
       concepts/resources/revisions.md: concepts/serving-resources/revisions.md
       serving/revision-gc.md: serving/revisions/revision-developer-config-options.md

docs/eventing/brokers/broker-developer-config-options.md

@@ -33,6 +33,6 @@ spec:
 
 - You can specify any valid `name` for your broker. Using `default` will create a broker named `default`.
 - The `namespace` must be an existing namespace in your cluster. Using `default` will create the broker in the `default` namespace.
-- You can set the `eventing.knative.dev/broker.class` annotation to change the class of the broker. The default broker class is `MTChannelBasedBroker`, but Knative also supports use of the `Kafka` and `RabbitMQBroker` broker class. For more information see the [Apache Kafka Broker](../brokers/broker-types/kafka-broker/README.md) or [RabbitMQ Broker](../brokers/broker-types/rabbitmq-broker/README.md) documentation.
+- You can set the `eventing.knative.dev/broker.class` annotation to change the class of the broker. The default broker class is `MTChannelBasedBroker`, but Knative also supports use of the `Kafka`. For more information see the [Apache Kafka Broker](../brokers/broker-types/kafka-broker/README.md) documentation.
 - `spec.config` is used to specify the default backing channel configuration for Channel based Broker implementations. For more information on configuring the default channel type, see the documentation on [Configure Broker defaults](../configuration/broker-configuration.md).
 - `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).

docs/eventing/brokers/broker-types/README.md

@@ -17,8 +17,3 @@ The following is a list of Brokers provided by the community or vendors:
 ### Knative Broker for Apache Kafka
 
 This Broker implementation uses [Apache Kafka](https://kafka.apache.org/) as its backing technology. For more information, see the [Knative Broker for Apache Kafka](./kafka-broker/README.md) documentation.
-
-### RabbitMQ broker
-
-The RabbitMQ Broker uses [RabbitMQ](https://www.rabbitmq.com/) for its underlying implementation.
-For more information, see [RabbitMQ Broker](./rabbitmq-broker/README.md) or [the docs available on GitHub](https://github.com/knative-extensions/eventing-rabbitmq).

docs/eventing/brokers/broker-types/channel-based-broker/README.md

@@ -1,7 +1,7 @@
 # Channel based Broker
 
 The Channel based Broker (`MTChannelBasedBroker`) uses [Channels](../../../channels) for event routing. It is shipped by default with Knative Eventing.
-Users should prefer native Broker implementations (like [Knative Broker for Apache Kafka](../kafka-broker/README.md) or [RabbitMQ Broker](../rabbitmq-broker/README.md)) over the MTChannelBasedBroker and Channel combination because it is usually more efficient as they reduce network hops for example. 
+Users should prefer native Broker implementations (like [Knative Broker for Apache Kafka](../kafka-broker/README.md) over the MTChannelBasedBroker and Channel combination because it is usually more efficient as they reduce network hops for example. 
 ## Prerequisites
 
 * You have Knative Eventing installed.

docs/eventing/sources/README.md

@@ -37,7 +37,6 @@ All Sources are part of the `sources` category.
 | [GitLab](https://github.com/knative/docs/tree/main/code-samples/eventing/gitlab-source) | Beta | Knative    | Registers for events of the specified types on the specified GitLab repository, and brings those events into Knative. The GitLabSource creates a webhooks for specified [event types](https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#events), listens for incoming events, and passes them to a consumer. See the [GitLab Source](https://github.com/knative/docs/tree/main/code-samples/eventing/gitlab-source) example for more details.  |
 | [KogitoSource](https://github.com/knative-extensions/eventing-kogito) |  Alpha | Knative    | An implementation of the [Kogito Runtime](https://docs.jboss.org/kogito/release/latest/html_single/#proc-kogito-deploying-on-kubernetes_kogito-deploying-on-openshift) custom resource managed by the [Kogito Operator](https://github.com/kiegroup/kogito-operator). |
 | [PingSource](ping-source/README.md) | Stable | Knative    | Produces events with a fixed payload on a specified [Cron](https://en.wikipedia.org/wiki/Cron) schedule. See the [Ping Source](ping-source/README.md) example for more details. |
-| [RabbitMQ](https://github.com/knative-extensions/eventing-rabbitmq) | Stable | Knative | Brings [RabbitMQ](https://www.rabbitmq.com/) messages into Knative.
 [RedisSource](https://github.com/knative-extensions/eventing-redis/tree/{{version}}/source) | Alpha | Knative | Brings Redis Stream into Knative.
 | [SinkBinding](../custom-event-source/sinkbinding/README.md) | Stable | Knative    | The SinkBinding can be used to author new event sources using any of the familiar compute abstractions that Kubernetes makes available (e.g. Deployment, Job, DaemonSet, StatefulSet), or Knative abstractions (e.g. Service, Configuration). SinkBinding provides a framework for injecting `K_SINK` (destination address) and `K_CE_OVERRIDES` (JSON cloudevents attributes) environment variables into any Kubernetes resource which has a `spec.template` that looks like a Pod (aka PodSpecable). See the [SinkBinding](../custom-event-source/sinkbinding/README.md) example for more details. |
 

docs/install/operator/knative-with-operator-cli.md

@@ -218,14 +218,6 @@ see how you can configure Knative Eventing with different event sources:
         kn operator enable eventing-source --kafka --namespace knative-eventing
         ```
 
-=== "RabbitMQ"
-
-    1. To install the eventing source RabbitMQ, run the following command:
-
-        ```bash
-        kn operator enable eventing-source --rabbitmq --namespace knative-eventing
-        ```
-
 === "Redis"
 
     1. To install the eventing source Redis, run the following command:

docs/install/operator/knative-with-operators.md

@@ -526,33 +526,6 @@ see how you can configure Knative Eventing with different event sources:
 
         Where `<filename>` is the name of the file you created in the previous step.
 
-=== "RabbitMQ"
-
-    To configure Knative Eventing to install RabbitMQ as the event source,
-
-    1. Add `spec.source.rabbitmq` to your Eventing CR YAML file as follows:
-
-        ```yaml
-        apiVersion: operator.knative.dev/v1beta1
-        kind: KnativeEventing
-        metadata:
-          name: knative-eventing
-          namespace: knative-eventing
-        spec:
-          # ...
-          source:
-            rabbitmq:
-              enabled: true
-        ```
-
-    1. Apply the YAML file by running the command:
-
-        ```bash
-        kubectl apply -f <filename>.yaml
-        ```
-
-        Where `<filename>` is the name of the file you created in the previous step.
-
 === "Redis"
 
     To configure Knative Eventing to install Redis as the event source:

docs/install/yaml-install/eventing/install-eventing-with-yaml.md

@@ -200,13 +200,6 @@ Follow the procedure for the Broker of your choice:
     !!! warning
         In order to use the KafkaChannel, ensure that it is installed on your cluster, as mentioned previously in this topic.
 
-=== "RabbitMQ Broker"
-
-    * Install the RabbitMQ Broker by following the instructions in the
-    [RabbitMQ Knative Eventing Broker README](https://github.com/knative-extensions/eventing-rabbitmq/tree/main/broker).
-
-    For more information, see the [RabbitMQ Broker](https://github.com/knative-extensions/eventing-rabbitmq) in GitHub.
-
 ## Install optional Eventing extensions
 
 The following tabs expand to show instructions for installing each Eventing extension.