You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
Since the RequestReply resource needs a trigger to every pod, rather than to the deployment as a whole, we need to create an InitContainer which creates the trigger to the current pod. The trigger should look like:
apiVersion: eventing.knative.dev/v1kind: Triggermetadata:
name: <generated name>namespace: <pod namespace>spec:
brokerRef: <brokerRef from the RequestReply resource>subscriber: <the RequestReply deployment>triggers:
- cesql: "EXISTS <the name of the replyid for the RequestReply resource> AND KN_VERIFY_CORRELATION_ID(<the name of the replyid for the RequestReply resource>, <the secret names for the resource listed out>)"
Hi @chaliuu, I’d love to collaborate on this issue if you’re interested. I’ve been trying to grasp some related concepts, and I believe working on this together could be really helpful. Let me know what you think!
Problem
Since the RequestReply resource needs a trigger to every pod, rather than to the deployment as a whole, we need to create an InitContainer which creates the trigger to the current pod. The trigger should look like:
Persona:
Which persona is this feature for?
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
Additional context (optional)
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: