Pipe Runs
Pipekit Pipes collect workflow runs in a logical group. You can view all runs of a given workflow in a Pipe, even across Kubernetes clusters.
Last updated
Pipekit Pipes collect workflow runs in a logical group. You can view all runs of a given workflow in a Pipe, even across Kubernetes clusters.
Last updated
You can view the runs of a Pipe by going to the and clicking on the Pipe you wish to view the runs of.
From here you can see all past runs of the Pipe. The view allows you to understand what triggered the run, the cluster the run ran on, the status of the run, the current progress of the run (if still running), any output message from Argo Workflows, the time the run started, and the duration of the run.
You can also see past runs in the same way. Just click the Pipe you are interested in. If the underlying workflow was a Cron Workflow, you can see information about the cron schedule as well as the standard Pipe run information.
If a run is still running, you can stop it by clicking the checkbox to the left of the run, and then clicking the Stop button at the top of the page. This will gracefully stop the run, and the run will be marked as Stopped in the list of runs.
You can resubmit a run by clicking the checkbox to the left of the run, and then clicking the Resubmit button at the top of the page. This will create a new run of the workflow, with the same parameters as the original run.
You can view more information about a given run by clicking on the run. This will take you to the run graph for the run. From here you can see the for the run, the for the run, and the for the run.
Pipekit will retain all runs for a Pipe. There is no limit to the number of runs that will be retained or the time period that they will be retained for.