-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
False
-
0
-
0%
-
Undefined
-
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
- is related to
-
-
- Accepted
-
