React to KFP Kubernetes resources instead of Argo workflows

[jmendesky]

Overview

Currently, the EventSource server listens to finishing Argo Workflows. Argo Workflows are implementation details of KFP and, therefore, not first-party objects. Furthermore, KFP produces different kinds of workflows depending on whether the run is triggered by a schedule or a rerun.

Instead, the EventSource server could listen to ScheduledWorkflow KFP resources. These resources contain all the information needed.

Implementation notes

• Spec.trigger.lastWorkflowIndex is the last known triggered pipeline run. In order to store whether an event has been processed, the EventSource Server would need to write an annotation to the resource that contains the last processed workflow.

Open questions

• Do reruns create the same status entries as scheduled runs?