Default to a single RabbitMQ cluster per Knative Eventing installation

This is what most users expect. Without this, the Messaging Topology Operator will not be able to manage objects from a different namespace. The implications are that all Brokers / Triggers / Sinks need to be created in the same namespace as the RabbitmqCluster. This annotation addresses that limitation. More context: - knative-extensions/eventing-rabbitmq#454 - rabbitmq/messaging-topology-operator#201 Signed-off-by: Gerhard Lazu <[email protected]>
gvmw · Dec 1, 2021 · 7e58c4a · 7e58c4a
1 parent 6a71737
commit 7e58c4a
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/docs/eventing/broker/rabbitmq-broker/README.md b/docs/eventing/broker/rabbitmq-broker/README.md
@@ -46,6 +46,9 @@ To use the RabbitMQ Broker, you must have the following installed:
         kind: RabbitmqCluster
         metadata:
           name: <cluster-name>
+          annotations:
+            # A single RabbitMQ cluster per Knative Eventing installation
+            rabbitmq.com/topology-allowed-namespaces: "*"
         ```
         Where `<cluster-name>` is the name you want for your RabbitMQ cluster,
         for example, `rabbitmq`.