Every run on the cluster shows up here.
CronWorkflow children, argo submit from somebody's laptop, whatever fires at 3am. They turn up in a section of their own, with the same logs, the same failure banner and the same email.
Nothing has to move first.
A tool that only knows about the workflows you moved into it is worth nothing until you have moved them.
The connector watches every namespace it serves from the moment it is installed. The runs on this page are workflows you have not touched.
The runs nobody dispatched from here
Cron schedules, argo submit, and whatever else on the cluster has a kubeconfig. They start runs you never opened dagweave for, and those turn up anyway, in a section of their own.
- Each one is named for the namespace and object it is on the cluster.
- The failure banner, the per-step logs and the artifact links are the ones a dispatched run gets.
- Failure email goes out for it too, with a link straight into the run.
Show a run to someone with no cluster access
Reading a run on the cluster takes cluster access. A dagweave account is enough here.
- No kubeconfig, no port-forward, no VPN.
- You choose which namespaces the connector serves.
The logs outlive the pod
Pod garbage collection takes the logs with it. kubectl logs against a pod that was cleaned up at 3am gives you nothing back. The collector already shipped those lines wherever you told it to put them.
- Logs go to your own S3, Loki or HTTP sink, or dagweave keeps them for you.
Open one on the canvas
A run you never started still points at a definition. Pull that definition back through the connector and it opens as a graph, every field editable, and goes to your repo as ordinary YAML.
- A CronWorkflow nobody has opened in years becomes a graph somebody can read.
- Editing one is a small diff against a file you own.
See the runs you already have.
dagweave is in early access. Leave an email and we will bring you on as we open it up.