abundant-football-23028
02/26/2024, 8:09 PMabundant-football-23028
02/26/2024, 8:10 PMabundant-football-23028
02/26/2024, 8:12 PMv3.4
, it looks like it's still outstanding (even though that version is out), so, if the two are the same, then that means it's still blocked.abundant-football-23028
02/26/2024, 8:14 PMabundant-football-23028
02/26/2024, 8:15 PMsquare-wire-39606
02/26/2024, 8:26 PMouterbounds
.
re: argo-events
in one k8s namespace - are you planning on running the argo-webhook
, event-bus
and sensors
- all in a single but different namespace to the one that deploys the flows?abundant-football-23028
02/26/2024, 8:45 PMargo-webhook
and event-bus
were deployed by the parameterized Helm Chart into the namespace specific to Argo Events, and then adding the @trigger
decorator caused the associated sensor
to be deployed in the Argo Workflows namespace. With that configuration, the UI showed the sensor
as not wired up correctly (compared to the example deployed with the Helm Chart).abundant-football-23028
02/26/2024, 8:48 PMKUBERNETES_NAMESPACE
is a larger effort, but I'm curious if there is value in being able to pass in a namespace that is specific to Argo Events for the few integration points (@trigger
being one of them).abundant-football-23028
02/26/2024, 8:49 PMsquare-wire-39606
02/28/2024, 4:21 PMKUBERNETES_NAMESPACE
at the right places in this file to point to your alternate namespace - are you able to get everything working?abundant-football-23028
02/28/2024, 6:41 PMworkflowTemplateRef
, it wouldn't work because Argo Workflows doesn't support that, yet.square-wire-39606
02/28/2024, 6:50 PMtrigger_workflow_template
is used to trigger the workflow outside of Argo Events by directly invoking the kubernetes API to launch an already deployed workflow templatesquare-wire-39606
02/28/2024, 6:53 PMabundant-football-23028
02/28/2024, 7:00 PMabundant-football-23028
02/28/2024, 7:00 PM