DataSet HealthChecks contain a reference to existing KubeETL Workflows. Once the Workflow is added as a HealthCheck, the DataSet Reconciler will mark the Workflow with the etl.dataworkz.nl/healthcheck label, which value indicates the DataSet(s) that use the Workflow as HealthCheck. Any time the Workflow is updated, a reconciliation event is also send to the DataSet(s).
Once the Workflow has created a valid Argo Workflow, and the status of the Argo Workflow is known, the DataSet reconciler will check whether the Argo Workflow succeeded. If so, it will mark the DataSet health as Healthy. If the Argo Workflow failed, it will be marked as unhealthy. Otherwise it will mark at as unknown, which can occur if an error occurred along the way.
ThijsKoot
commented
3 years ago
Fixes #17
DataSet HealthChecks contain a reference to existing KubeETL Workflows. Once the Workflow is added as a HealthCheck, the DataSet Reconciler will mark the Workflow with the
etl.dataworkz.nl/healthchecklabel, which value indicates the DataSet(s) that use the Workflow as HealthCheck. Any time the Workflow is updated, a reconciliation event is also send to the DataSet(s).Once the Workflow has created a valid Argo Workflow, and the status of the Argo Workflow is known, the DataSet reconciler will check whether the Argo Workflow succeeded. If so, it will mark the DataSet health as Healthy. If the Argo Workflow failed, it will be marked as unhealthy. Otherwise it will mark at as unknown, which can occur if an error occurred along the way.
Signed-off-by: Lennard Eijsackers lennardeijsackers92@gmail.com