Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-9883

Discovery service is not considering the GVK brokers.v1.eventing.knative.dev

XMLWordPrintable

    • 2023 Week 36-38 (from Sep 4)

      According to https://sonataflow.org/serverlessworkflow/latest/cloud/quarkus/kubernetes-service-discovery.html the GVK brokers.v1.eventing.knative.dev cannot be used when using custom knative function; it is not considered by the service discovery

        - name: sendCloudEvent
    type: custom
    operation: knative:brokers.v1.eventing.knative.dev/m2k/default?asCloudEvent=true

      (m2k being the namespace and default the name of the broker)
      The following error is logged when using this function:

      WorkItem execution failed with error code The Knative service 'brokers.v1.eventing.knative.dev/m2k/default' could not be found.

      Here is the available broker:

      $ kubectl -n m2k get broker
NAME      URL                                                                    AGE   READY   REASON
default   http://broker-ingress.knative-eventing.svc.cluster.local/m2k/default   17h   True

      When using keventing, it would be best if all events transit via the broker instead of addressing the function directly.

              wmedvede@redhat.com Walter Medvedeo
              rh-ee-gfarache Gabriel Farache
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: