jianrongzhang89 commented on PR #467:
URL:
https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/467#issuecomment-2185434913
> @jianrongzhang89 I just tested with adding only the following to the
sonataflowplatform:
>
> ```
> eventing:
> broker:
> ref:
> name: kafka-broker
> namespace: sonataflow-infra
> apiVersion: eventing.knative.dev/v1
> kind: Broker
> ```
>
> The triggers are created:
>
> ```
> $ oc get trigger -A
> NAMESPACE NAME
BROKER SUBSCRIBER_URI AGE READY REASON
> orchestrator data-index-jobs-2ac1baab-d856-40bc-bcec-c6dd50951419
kafka-broker 6m51s
> orchestrator
data-index-process-definition-634c6f230b6364cdda8272f98c5d58722 kafka-broker
6m51s
> orchestrator
data-index-process-error-2ac1baab-d856-40bc-bcec-c6dd50951419 kafka-broker
6m51s
> orchestrator
data-index-process-node-2ac1baab-d856-40bc-bcec-c6dd50951419 kafka-broker
6m51s
> orchestrator data-index-process-sla-2ac1baab-d856-40bc-bcec-c6dd50951419
kafka-broker 6m51s
> orchestrator
data-index-process-state-2ac1baab-d856-40bc-bcec-c6dd50951419 kafka-broker
6m51s
> orchestrator
data-index-process-variable-6f721bf111e75efc394000bca9884ae22ac kafka-broker
6m51s
> orchestrator
jobs-service-create-job-2ac1baab-d856-40bc-bcec-c6dd50951419 kafka-broker
6m51s
> orchestrator
jobs-service-delete-job-2ac1baab-d856-40bc-bcec-c6dd50951419 kafka-broker
6m51s
> ```
>
> But they are not in the same namespace as the broker, is that normal?
>
> Then, I create the kafka broker:
>
> ```
> $ oc get broker -A
> NAMESPACE NAME URL
AGE READY REASON
> sonataflow-infra kafka-broker
http://kafka-broker-ingress.knative-eventing.svc.cluster.local/sonataflow-infra/kafka-broker
5m15s True
> ```
>
> But the triggers are never ready, I guess because they should be in the
same namespace as the broker?
Thank you for catching this. This issue is fixed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
