Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-2440

Extend subscriber for subscription/trigger to other resources apart from KSVC

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Normal
    • None
    • None
    • Developer Experience

    Description

      Description: currently we visualise only subscriber as KSVC for both Subscription/triggers where Subscription/triggers are visualised as connector between channel/broker and KSVC.

      spec:
       channel:
        apiVersion: messaging.knative.dev/v1
        kind: InMemoryChannel
        name: in-memory-channel
       subscriber:
        ref:
         apiVersion: serving.knative.dev/v1
         kind: Service
         name: hello-openshift

      We would need to extend these to other resources (any Addressable resource) as well and Subscription does support other options i.e `delivery` with `deadLetterSink` etc . Even all of these resources should be visualised in Topology

      spec:
       channel:
        apiVersion: messaging.knative.dev/v1
        kind: InMemoryChannel
        name: default
       delivery:
        retry: 5
        backoffPolicy: exponential # or linear
        backoffDelay: "PT0.5S" # or ISO8601 duration
        deadLetterSink:
        ref:
         apiVersion: serving.knative.dev/v1
         kind: Service
         name: error-handler
       subscriber:
        uri: http://doesnotexist.default.svc.cluster.local

       

      https://knative.dev/docs/eventing/event-delivery/

      https://knative.dev/docs/eventing/triggers/ 

      Attachments

        Issue Links

          Activity

            People

              sdoyle@redhat.com Serena Nichols
              jakumar jaivardhan Kumar
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: