knative
RequestReply: Create InitContainer
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/v1
kind: Trigger
metadata:
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>)"
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.
- https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
- https://stackoverflow.com/a/72218928
- #7912
Hi @Cali0707, @chaliuu, is anyone currently working on this issue? If not, I’d love to contribute!
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!