soareslo:~$kubectl get deployment.apps -n knative-eventing
NAME READY UP-TO-DATE AVAILABLE AGE
eventing-controller 1/1 1 1 7d1h
eventing-webhook 1/1 1 1 7d1h
kafka-broker-dispatcher 1/1 1 1 7d1h
kafka-broker-receiver 1/1 1 1 7d1h
kafka-controller 1/1 1 1 7d1h
kafka-webhook-eventing 1/1 1 1 7d1h
pingsource-mt-adapter 0/0 0 0 7d1h
rabbitmq-broker-controller 1/1 1 1 9m4s
rabbitmq-broker-webhook 1/1 1 1 9m4s
soareslo:~$kubectl get brokers
NAME URL AGE READY REASON
lasbroker http://kafka-broker-ingress.knative-eventing.svc.cluster.local/default/lasbroker 7d2h True
rabbitmqbroker 2m54s
Below you can see the broker description without errors.
soareslo:~$kubectl describe broker rabbitmqbroker
Name: rabbitmqbroker
Namespace: default
Labels: <none>
Annotations: eventing.knative.dev/broker.class: RabbitMQBroker
eventing.knative.dev/creator: masterclient
eventing.knative.dev/lastModifier: masterclient
API Version: eventing.knative.dev/v1
Kind: Broker
Metadata:
Creation Timestamp: 2021-11-25T12:24:49Z
Generation: 1
Managed Fields:
API Version: eventing.knative.dev/v1
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:eventing.knative.dev/broker.class:
f:kubectl.kubernetes.io/last-applied-configuration:
f:spec:
.:
f:config:
.:
f:apiVersion:
f:kind:
f:name:
f:namespace:
Manager: kubectl-client-side-apply
Operation: Update
Time: 2021-11-25T12:24:48Z
Resource Version: 13195895
UID: 003cf445-af3c-4519-8237-78e301f505f6
Spec:
Config:
API Version: v1
Kind: Secret
Name: azureservicebus
Namespace: knative-eventing
Events: <none>
soareslo:~$
Hey Anderson,
Support for the standalone broker is been dropped so I recommend using the normal broker and following the instructions here:
eventing-rabbitmq/operator-based.md at main · knative-sandbox/eventing-rabbitmq (github.com)
Let me know if with this one things go as expected :)
--
You received this message because you are subscribed to the Google Groups "Knative Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
knative-user...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/knative-users/e82d21d5-1135-4d01-8c73-6657fd3a71a2n%40googlegroups.com.
Yep, that’s exactly it. It seems that external queues are a known need for the RabbitMQ Cluster and Message Topology Operators, but is not clear when they are going to be implemented.
Sent from Mail for Windows
Hi Anderson,
The Knative RabbitMQ Source enables pulling events from any RabbitMQ queue.
This issue provides some more context regarding the Knative RabbitMQ Broker.
Cheers,
Sameer
To view this discussion on the web visit https://groups.google.com/d/msgid/knative-users/BN6PR05MB325130CC3D78D62B164CEBD7B2629%40BN6PR05MB3251.namprd05.prod.outlook.com.